I am working in visual studio 2010 on many projects, all projects are similar, and are modified from 1 project which was used as a template, but when I was trying to rename the controls to a new name for this specific project, it takes forever to rename controls, and when it has over 100 controls it takes about 4 hours!
The problem has been posted here but no solution seemed to work.
After hours of trying everything possible, this worked:
In Visual Studio, go to Tools>Options, Under Windows form designer > Refactoring, change EnableRefactoringOnRename to False.
This will speed up amazingly from 12 seconds to less than 1 second per control!
If you ever need this as a function to refactor automatically any reference to this control in your project, you can always go back and enable it.
Related
We have a large solution (112 projects) in VS2013 Ultimate.
I love the Code Map feature, however when I am dragging types onto a Code Map dgml it insists on building the solution - even though I have not made any changes.
I can't see many options for this great feature, but is there anyway to tell it to stop building the solution everytime I add a type to the diagram?
This is a known issue and major complaint with Code Map in Visual Studio 2013. It affects certain types of projects (like ASP.NET ones) more than others because these projects always report that they have changes and need to be rebuilt.
The experience is improved in Visual Studio 2015 Enterprise, as we have added a "skip build" option.
We've made many improvements to CodeMap in Visual Studio 2015, so it's definitely worth getting it if you use Code Maps. Note that you can install VS 2015 along side VS 2013, so you don't have to migrate projects etc.
I see the code map document window in VS 2015 now contains a button labelled "Skip Build" which seems to solve this problem
I don't know when this started, but I discovered that Visual Studio 2013 Update 5 aborts when attempting to open properties for a project within a solution. It seems to only happen when we have more than one project in the solution.
I've been able to reproduce it in two circumstances:
The first project is C++ and the second project is Fortran. Right-clicking on the first project and selecting Properties crashes Visual Studio without a crash dump or any kind of pop-up notification. Visual Studio just ceases to exist. Right-clicking on the Fortran project brings up the property sheet without any problem.
The second circumstance is with two projects, both C++. In this case, I'm able to open properties successfully for the first project, but not for the second one.
In every case I've tried where there's a one-to-one solution and project, it's working fine. A colleague who's working with VS 2013 Update 4 verified that the crash occurs for him as well.
We don't know when this started, but historically, we've opened these property sheets many, many times. However, it's probably been a few months since I've worked on a mixed-language process, and same with my colleague.
I've turned on logging and there was a complaint in the log about two versions of the Desktop SDK having the same internal ID. I removed one of those altogether, but that didn't seem to affect anything. It's also not clear if that error has any relationship to the crash.
I've also done a repair on Visual Studio, and that did not correct the problem.
I've also tried deleting the .suo and .user files. Again, no luck.
I've done quite a bit of googling but haven't found anything that matches this specific problem.
Any ideas?
Thank you,
Doug
My solution has more than million files.
When I try to open solution with Visual Stodio.Net 2013, it tries to load all files then crashes.
If I first hide files in windows explorer then I can open it but it takes 30 minutes to set hide or unhide.
I know there is a setting in Visual Studio but couldn't remember it.
Is there any idea?
Thanks in advance
Visual Studio simply can't scale to a project of this size. There is no hard limit on the number of files but one million is certainly too many. Try breaking your project into several projects each containing a more reasonable number of files.
Note: having a million files in a project seems quite extreme.
How to open multiple projects at time in VS2010?
Have several instances of VS (this may tax your RAM, but it is no problem if you have 2 GB or more, I often have several Visual Studios with large solutions started)
Add the projects you want to have opened to one solution (right click the solution in Solution explorer, it is there).
Visual Studio has two "project" buckets to structure your work. The top level is called the solution level. One solution can have any number of projects. So, create a solution, and add your projects to your solution. See http://msdn.microsoft.com/en-us/library/Ee817674(pandp.10).aspx. Although the article is outdated, the concepts still apply
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.