I am working with 10 other people on a VS, C# , Xaml project but recently a branch someone pushed to the master broke the Solution Explorer and I am not able to get it to show the elements under MainWindow.xaml.cs again
No one cares too much about this because the controls are still working if we call them by code and our designers use Blend to edit the design (note: all the controls appear fine in Microsoft Blend for Visual Studio)
But it is troublesome for me to have to open Blend just to adjust a minor design flaw instead of doing it inside Visual Studio directly.
I tried googling but haven't found anything related to my issue yet.
Working Image Example
Broken Image Example
Related
I've been maintaining a suite of code for my employer for several years, and a new programmer started here recently that I've been training. As described in the subject, the Run Designer feature/button (as seen in screenshot below) isn't available to him for forms that I've overridden and customized. The Grid Designer is essential for modifying the data displayed by the grid. We've spent many days trying to figure this out, so I'm posting it here in case anyone else encounters this issue.
We're using DevExpress 14.1.6 with Visual Studio 2019 [16.11.11] (this pairing isn't officially supported). Both of us are on Windows 10.
Navigate to "DevExpress 14.1\Components\Tools\Components" in your program files. Open the file DXDesignKeys.exe and check both checkboxes (Enable design-time form skinning, and Enable visual inheritance for Developer Express controls used in Visual Studio) in the user interface, then click Apply and Close.
I am having problem in using the source view of an asp.net page in VS.net 2008 IDE. I am not using Design view at all. IDE hangs a bit every now and then, when I use intellisense in it, and I scroll the page.
Please throw some light on it.
Such issues doesnt come up while editing the HTML page, and while editing same asp.net page with the HTML editor which can be configured using Tools -> Options menu option.
Read this Post
This might help to make your visual studio a bit faster in general. I am not very sure about the exact reason for the behavior you mentioned of your Visual Studio.
I suspect that it has something to do with Graphical Interfaces like Toolbox etc.
Thanks
I've had problems like that with Visual Studio before. The intensity of the problems seem to multiply exponentially as the size of the file I work with gets larger.
Here's what I'd reccomend:
Check and make sure Visual Studio is fully updated (Help > Check For Updates) ; there have been some patches released and they will help you immensly!
If your code has any breakpoints, disable them all and start afresh later (Debug > Disable All Breakpoints)
If that fails, here are some more optimizations you can try.
In my case, I think longer file is the culprit. I think partial page concept should be applicable to asp.net page too.
We have a project in our solution that houses a test application with multiple windows forms. Every time I open up a form in the form editor, Visual Studio goes out to lunch, chewing up an entire processor... until I kill the process.
I tried to port over to a new project, thinking something in one of the forms, or the project file was causing the issue, but the new project exhibited the same behavior. In a new solution, though, the forms behave properly.
We did recently convert the solution from 2005 to 2008, but I couldn't find any similar conversion issues.
Anyone else experience something similar?
One of the operations which happens during form load is that form controls in your project which appear on the form are instantiated in the Visual Studio process. Given that they are running in the process it's possible for them to do bad things to Visual Studio like cause it to crash or hang.
You could rule this in or out by opening the form and attaching a debugger to visual studio and seeing if any of your controls are in a timely / infinite loop.
All projects get searched to find any custom controls to put in the toolbar, I don’t know if this is part of your problem.
A few times a day my VS2008 SP1 freezes if I edit XAML code. It just got stuck and I have to kill the process.
It seems to be a problem with the IntelliSense or the spell-checking or whatever process is going on while I edit code.
The problem is very apparent if I copy+paste some code. Even if it is just one word. Many times VS2008 adds some additional commands in the code and messes things up completely.
This never happened with C# code only with XAML it does get stuck.
One more thing: It seems the problem only occurs when I edit control templates. I added a few control templates from the MSDN pages to my project. When I edit them - even doing simple things like changing brush colors - Visual Studio freezes (sometimes). So it seems it's not a general XAML problem it happens with control templates only.
You could try this update: Installing DExplorer after VS 2008 breaks xaml intellisense
EDIT: You could try closing the Properties window when editing XAML, it helped me before with ASP.NET.
Some other links:
Xaml Editor Crashes after Visual Studio 2008 SP1
Using the Source Code Editor for XAML in Visual Studio
After having this problem and hunting around on the interwebs I found this vsnet-crashes-when-editing-xaml
Which said, in summary, if you edit a xaml resource while something that uses said resource is open in a designer, then you'll be sorry.
So you can avoid the problem by
Closing the other designer windows;
Installing hotfix KB958017.
I'm a Silverlight newbie. Just downloaded version 3.0 after the Mix announcement. I'm running VS 2008 SP1. When I select a design element in the preview pane or in XAML, the properties window is disabled and displays
Property Editing Not Available
I can open the solution in Blend and have no problems with it's property editor. So within Visual Studio, I'm forced to enter everything in the XAML pane and rely on Intellisense.
Is something wrong with my installation or environment? Or am I supposed to switch back and forth between Expression Blend and Visual Studio (I can't believe that should be the case).
There is nothing wrong with your installation or environment. The XAML designer/editor in VS2008 is very limited in what it offers for XAML editing whatever the version of Silverlight, being really just a rendering engine at the moment.
Expression Blend is the visual editor of choice for now - there are 3rd party editors available (such as XAMLCruncher and Kaxaml) but they don't really support XAML with code-behind classes.
Additionally the Blend 3 preview that was released to support SL3 seems to have a few improvements which address previously inferior experience of directly editing XAML in Blend (notably IntelliSense).
I had the same problem with Visual studio 2010 and Silverlight 5.0. It was intermittent.
One thing I found to help is to switch the XAML page to show Design view and then switch back to Code view or vice versa. If you have hybrid view, just temporarily switch.
I did that and it just worked fine. I do n't know the reason it worked but it did.
Is something wrong with my installation or environment? Or am I supposed to switch back and forth between Expression Blend and Visual Studio (I can't believe that should be the case).
You'll find you need to do that a lot for both Silverlight and WPF if you want to make full use of the UI controls.
I find VS incredibly slow and clunky for designing and rendering XAML and much prefer Expression. Switching between the two is no big deal as really one's for code and ones for design.
I haven't download the Silverlight 3 Beta yet, but the Silverlight 2 designer intergration in visual studio is very poor.
VS 2010 is suppose to have better support for XAML Editing in WPF and Silverlight. So for now, you'll have to find the right balance between Blend and VS.
SilverLight 3.0 beta just shipped. VS2008 SP1 shipped last year. It would be surprising if it supported SilverLight 3.0 out of the box, and more suprising if the VS support that ships with SilverLight 3.0 beta were not "beta" quality.
If you find problems, then be certain to report them to Microsoft.