I have a problem with Visual Studio 2012 that I'm hoping someone can help me out with.
Visual Studio hangs when I try to modify a XAML file. Admittedly my solution contains over fifty projects and I am running ReSharper and StyleCop. This is my first day in a new job and my first experience with XAML so I'm trying to make a good impression!
What can I try to sort out this issue?
Thanks in advance, Mark
After a bit of googling, I found the solution to my problem here: http://weblogs.asp.net/fmarguerie/archive/2009/01/29/life-changer-xaml-tip-for-visual-studio.aspx
Try to suspend/uninstall Resharper and all other plug-ins for Visual Studio. This worked for me whereas all other methods did not.
Also try to run VS with /SafeMode flag and see if it works properly.
This is still issue in 2013 (as of May 2016). The suggested solution above is not helping.
With my Visual Studio 2012.4 I found that while opening XAML in design mode, XDesProc was using 2gb of my RAM and 25% of CPU (i7 8 core), I resolve the problem by turning off the data loading in View Model’s constructor if in design mode. Loading the ItemsSources of my many Comboboxes just bogged down the designer. This way I can still have my designer. Don't forget to import System.Windows and System.ComponentModel in your ViewModel and add these code below in the constructor
If DesignerProperties.GetIsInDesignMode(New DependencyObject) Then
‘ Do nothing
Else
‘ Load the data
End If
Related
The VS2013 XAMLX designer is very slow with medium sized xaml workflows.
About 10 to 40 seconds for each small change we make.
We don't want to disable the designer and work in xaml directly.
This is what we have done and tried so far (without success)
Disable Resharper
SSD Drive to speed up I.O.
Make sure the machine has enough memory and cpu...
Has anyone got more ideas on how to speed this up?
UPDATE (23-11)
This is a little convoluted, though it might shed some light.
I installed VS2015, which made a huge difference, though the workflows wouldnt work in IIS. The problem was due to a windows update which caused an error. Check this link https://support.microsoft.com/en-us/kb/3118750
I was getting errors like this:
FileLoadException: A procedure imported by 'Microsoft.VisualBasic.Activities.Compiler.dll' could not be loaded
So, I am guessing that validation was turned off while the compiler had issues.
It seems like VS2010 had a setting to turn off validation, though I cant find how to do that in 2013
Does this help at all, can anyone suggest a solution?
I'm using VB.NET in VS2008 professional. Just installed Coderush Xpress 11.2.10. Code formatting and intellasist doesn't work.
I tried Edit->Advanced->Format Document but VS keeps formatting in its standard VB way without coderush configuration.
Intellasist never shows nothing. Even with intellisense deactivated in VS.
Can somebody help me? Thanks.
I regret to inform you that neither Intellassist nor Code Formatting for Visual Basic is available in the free CodeRush Xpress version.
I'm working on a VB.Net project and using SVN. I noticed that every time I open my main form, Visual studio slightly modifies my .resx file, which means that I keep having to re-commit it, which is quite annoying.
Has anybody experienced such problems? A diff file demonstrating the problem can be seen at http://synchronicity.svn.sourceforge.net/viewvc/synchronicity/trunk/Create%20Synchronicity/MainForm.resx?r1=272&r2=359&pathrev=359
Thanks,
CFP.
Bit late, but this sounds like a problem I raised with Microsoft around Image Lists:https://connect.microsoft.com/VisualStudio/feedback/details/428868/png-files-corrupted-in-an-imagelist-when-opening-and-closing-a-form
We are currently building a WPF solution in Blend 3 and Intellisense is extremely slow.
Visual Studio 2008 and 2010 beta 2 do not have any problems, Blend 2 did not have any issues either.
How would it be possible to disable Intellisense in the XAML editor.
Many Thanks,
KShaban
What was actually causing the problem for me was that my UI project had a lot of external assemblies referenced. Specifically, it was referencing some DevExpress Winforms stuff for reporting needs.
Once I refactored the UI project to not depend on those dependencies Blend started working great.
As a note, I attached a debugger to Blend while it was hanging and it seems that Blend keeps re-reflecting over those same assemblies. Also, the assemblies in question were not in the GAC.
The funny thing is VS2008 or VS2010 do not choke at all as far as intellisense on the same project.
Hope it helps.
We have 3 developers all using the same version (VS 2008 SP1) and we all use large VB projects (windows forms). From time to time, the IDE will have all sorts of issues such as locking up, crashing, and even not being able to drag a form object around or it will just instantly disappear.
On the largest of our projects (which is actually 5 projects in one solution file), a couple people here can only rebuild the project for testing 2 - 3 times before they have to close the studio and reopen it.
Has anyone else experienced this? Does this happen with large C# projects?
Yes, I experience this all the time! It has gotten better in 2008, if you can believe it.
I usually find that the reason has to do with an exception in my own code. The UI might bring in a custom control that does not behave well in design mode, causing the problem.
Sometimes, I will bring up a second execution of VS2008 and attach the debugger to the first execution of VS. Then, I can debug my own code as it is being run in the designer of the first instance. Often, an exception is thrown and I can fix my code to play better in the designer.
In other circumstances, I have no idea why it happens.
I have heard of people having this issue, however, I have never had an issue at all myself.
I have heard that a number of people trace the issues back to the use of ReSharper as the primary cause.
The most common problem I've had that causes the designer to crash is when I create a form where the only constructors require parameters.
To alleviate that, when I need the form only to be instantiated with parameters, I create a private parameterless constructor that the designer can use but which the form's consumers won't see.
I have personally experienced all sorts of designer wickedness with VS2008 sp1. I uninstalled the service pack to return stability to my dev environment. This is an unfortunate answer, but give it a try.
Only thing I've had close to this is the design view crashing and bringing up an error, formerly causing me to have to recreate the form and copy and paste the code across until I learnt how to fix it.
My problem was occurring because of me using ctrl+f a lot though. If you are using big files, this might be what's happening.