I have installed Visual studio 2012 on my system and after that my system is damn slow. Even Visual studio 2010 ( which was installed before) is very very slow. It takes 15 minutes to open. 5 minutes to buld a simple hello word program. I recently installed only Vs 2012 and Windows 7 SP1.
Please tell me how I can speed up VS 2010 ( not 2012). It has telerik controls added as well. I am ready to remove it if necessary.
Thanks
something tells me it might just be a slow pc?
EDIT: so as not to just leave a troll post, i recently got VS 2012 and it hasnt affected my load/build or compile times at all
If Vs 2012 Try this: Remove all the "UNUSED" MS Access or other data files in the App_Data folder - including any that are in sub folders. If you have old versions in App_Data or in any sub folders then Visual Studio will have to open all of them even if your website does not use them. In my case it took 2 - 3 minutes to open the website and even longer to close. I had 50 or so backups and test databases I kept in various folders just a archives. I just moved them to another folder in my website. Wow - Visual Studio now opens in a few seconds.
Related
I tried looking this up on the visual studio support site and apparently this should have been fixed. I am still experiencing periodic hanging while debugging.
I am running the most recent update of visual studio 2017: 15.2
I have tried disabling extensions (Resharper 2017 Ultimate, Developer Analytics, etc.) without any luck. Its very frustrating, because I end up having to end the Visual Studio task in task manager.
Has anyone else had similar issues with 15.2?
UPDATE
I found this on the MS site. I had looked up and down, but once I added a 15.2 search criteria it showed up.
I had issue with Visual Studio 2019 hangs while debugging. I have deleted .vs(hidden) folder. It works fine then.
The .vs directory can be found on the same directory where the solution file located. (It was hidden by default, we need to enable the visibility on file explorer setting at windows )
Updating to 15.2(26430.16) has solved this issue. I preformed the update almost 2 weeks ago and have not had an issue since.
Refactoring/renaming a control in Visual Studio Community 2015 (either in the form designer code file, or through the graphical designer) is very slow and each change uses an additional 60 MB of RAM memory.
I did read the Visual Studio 2015 C# rename horribly slow post, but that person's solution does not apply to me, because I did not add any extensions: this is Visual Studio "right out of the box".
open the project: 170 MB (the Designer is closed)
rename a control: 350 MB (in the code file)
revert the naming: 420 MB
rename a new control: 500 MB
After 2 or 3 renamings, I have to quit the application and open it again.
Many people must have encountered this, yet I don't see much discussion about it.
I just switched from VS 2010, which did not have this problem.
EDIT: I restarted the computer, no other programs running: same problem. Now Window 7 tells me: "Microsoft Visual Studio is busy / Microsoft Visual Studio is waiting for an internal operation to complete. ... "
Are there any solutions or workarounds?
Just curious how many people are actually running 2010 and what's your feedback so far?
Can I run 2010 concurrently with 2008 without issues?
Also, are 2008 projects 100% compatible with 2010 and if so should I just uninstall 2008?
Thanks for any feedback.
I've moved the whole development group for our project to VS2010 3 days after it came out. Before this I've been trying out the beta versions on my machine with some side projects.
From the experience I got I can say:
VS 2010 can easily run alongside VS
2008 on the same machine without any
issues whatsoever.
The projects
created in VS 2008 can be opened in
VS 2010. But when they are opened -
they will be updated to the new
format, and cannot be reopened in VS 2008. The changes aren't critical, so if it's necessary it is possible to
revert these changes. Possible, bt
not straightforward :)
This means that if you're working on a collaborative project, either the whole team moves to 2010, or you all stay with VS 2008. That doesn't mean you can't write your own projects in VS 2010 in parallel ^_^
UPD: I haven't met any projects that I wasn't able to convert using the conversion wizard. but just in case you can install VS 2010, convert your project, and see if it's all fine. If it is - work on it for a couple of days.. If you're completely satisfied - uninstall VS 2008 and feel good about it :D
Yes you can run 2010 concurrently with 2008. I wouldn't bet that every 2008 project can be opened/converted to a 2010 project otherwise Microsoft would have never spent so much time making the conversion wizard. The conversion wizard also mentions you should back up the files prior to conversion.
I have around 50 projects in Visual Studio 2005 that I am building a new development machine for and I'd like to slowly move those projects to VS 2008 but also have 2010 available for select new projects.
Can this work? Are there any gotchas for this sort of setup? Any general advice for running multiple versions of Visual Studio on the same system would be greatly appreciated. Specifically related to managing a controlled migration of projects to new versions but being able to selectively keep some on old versions.
I've got 7.1, 8, and 9 installed at the same time (well, and VB part of 6 as well) and I've not really had a problem opening projects file in the wrong version. The Visual Studio Solution files is "associated" with a particular version even if they all have the same extension of .sln, as you can see from its little icon. Microsoft Visual Studio Version Selector seems to handle individual project files (.vcproj) fine as well.
The only thing I've had is the individual source code files not opening up in the latest version like I want, but that's easily fixed with the click of a little button in VS Opions.
Microsoft have this to say:
Visual Studio supports the installation of Visual Studio .NET 2002, 2003, ... on the same computer.
In general, you should install the earliest release of Visual Studio first, and then install subsequent versions of Visual Studio in the order in which they were released.
Make sure when you open up the 2005 files you're doing it in 2005. To open them in another would require a conversion which would render them incompatible with the older compiler set-up. To aid this, structure whatever workspace you're using into 2005, 2008, and 2010 so as to minimize accidental chance of this.
Second, when you double click to open the projects, it will invariably attempt to open them with 2010. You'll have to start with VS#### instead of the solution/project unless you're in the 2010 workspace.
I have VC6, VB6, VS 2008, and VS2010 RC installed on Windows Vista. I cannot double click on the VC6 dsp files without VS2010 opening and asking to perform the conversion. The 2008 C# projects open in 2008 as long as I use the solution file. The 2008 project file opens in 2010 instead of 2008 even though the version selector is the default program. Most of the time I try to remember to open the desired version of Visual Studio and then open the project.
You can mitigate some of these issues by changing the default program associations in the control panel or the registry.
Update: This setup works on Windows 7 x64, with the addition of VS2013.
Yes it can work. I'm not sure if you have to install them in a particular order... but install them in order of the versions... 2005, 2008, 2010. Should be good to go.
I can't speak for 2010, but I have run 2005 and 2008 at the same time on my system without any fuss.
And I made the double-click mistake that wheaties warns about more than once :(
I have VS2005 & VS2008 running without any issues. I have had problems when working with betas, express editions & am assuming you don't have them.
I would say refrain from making too many changes to the setup of these editions, it should be fine.
I also had the same doubt. I work at my company which is still on VS 2008 and I want to personally use the VS 2010 and not risk the 2008. I installed the 2010 and it worked fine with the 2008. Just make sure you note the projects that are in 2005 and open them with the same accordingly.
The reason why it works is simple: if you open your solution file in Notepad, you'll see which version of VS is related to your project.
I've issue with VS08. I've got Web Application project (vb.net). Whenever I try to open an aspx or ascx (in Source view - just double clicking on Solution Explorer) the file opens, but VS hangs and is not responding. The only way to restart VS is then by killing it's process. And it happens all the time with these types of files. :/ Reinstall didn't work.
In addition, the only plugin I've installed with this instance of VS is ClearCase source control plugin.
This clearly looks like a problem with the "Microsoft Visual Studio Web authoring Component" program.
Simply pressing Change from Programs and selecting Repair fixed the issue for me.
Now I can use the design look also.
This happened for me when I installed Office 2010.
You should try to remove "Microsoft Visual Studio Web authoring Component" (from Programs).
I had the same problem and removed this component of Visual Studio (more about it here).
You'll loose the visual designer but VS won't hang anymore.
It could be a problem with the "Solution User Options" file (.suo) that lives in the same folder as the solution (.sln) file.
Try checking everything in, closing visual stuido, deleting this file and restarting.
May or may not help - you might not even have a solution after all!
Alternatively, are you using any anti-virus software? Commonly AV is set-up to check files as they are accessed. I seem to remember having issues with ours a while back, and stopping it checking files within my solution helped.
If you use Sophos I can help further, otherwise try stopping your AV scanning your solution's files.
You can try opening using other Visual Studio editor (right-click on the file, Choose Open With...)
There are many cases which may cause your vs2008 to hang. The only experience that caused my VS2008 to hang was right after installing Office2010. Once it happens, the only workaround is to kill Visual Studio in Task Manager. The root cause of this problem is that Office 2007 and the VS 2008 web designer both share a component, 32-bit MSXML5. When Office 2007 uninstalls or gets upgraded ie office2010, MSXML5 is removed yet Visual Studio still needs it.
There are many ways to fix this particular issue
1 - uninstalling Office 2010 and rebooting your machine; the issues will be resolved.
2 - if you still insist on using office 2010 (which will eventually happen) then go to your programs and right click on Microsoft Visual Studio Web Authoring tool and click on repair.
3 - You can simply remove Microsoft Visual Studio Web authoring Component completely from programs. Reinstall "Microsoft Visual Studio Web Authoring Component" from the VS2008 used. You can find the Web core designer from this particular path of your visual studio:
WCU\WebDesignerCore folder and run WebDesignerCore.exe
4 - If you are still experiencing some more issues the link below should sort it out
http://blogs.msdn.com/b/webdevtools/archive/2010/04/19/upgrade-or-uninstall-of-office-2007-might-cause-vs-2008-web-designer-to-hang.aspx
Wild shot, but try turning off Html Validation in Options. There was an issue with that at some point.
Turning off Html Validation didn't work. What I've noticed that before opening .aspx/.ascx file in solution memory usage (of VS) is for example 50k and when I double click i.e. Default.aspx to view Source then memory usage goes up to for example 150k and VS is not responding.
Everything did work last week. :/
I was having the same problem... Designer pages when opened hanged the VS.
I use VS2008 SP1.
I had installed Office 2010 AND UPON GOOGLING I FOUND THAT MICROSOFT VISUAL STUDIO WEB AUTORING COMPPONENT needed to be repaired.
If you install VS 2008 Beta on a clean machine, you will find Microsoft Visual Studio Web Authoring Component in the list of installed programs. You will also find that Program Files\Microsoft Web Designer Tools\Office12 and Program Files\Common Files\microsoft shared\OFFICE12 folders with some Office 2007 components even if you don't have Office 2007 installed.
What is Microsoft Visual Studio Web Authoring Component and why does it install Office 2007 components on my machine? The answer is that it is new HTML/ASP.NET design surface that is based on former FrontPages technologies, similar to Expression Web Designer. The designer was made into a separate component, but it was hard to fully separate code from Office libraries. So in VS 2008 designer is installed using separate setup which also installs a few Office libraries the designer relies upon. This means you will get Office 2007 updates offered to you via Microsoft Update although technically you don't have Office 2007 installed. This is because Microsoft Update recognizes shared components and will offer you related updates, so don't be alarmed or surprised. Office 2007 components are fully compatible with Office 2007 so you can freely install and uninstall Office 2007 or VS 2008 and both systems will continue working correctly. Designer is also compatible with Office 2003 and should not be affecting Office 2003 applications. If you observe any disrepancies, please report bug via Microsoft Connect ASAP and we will definitely investigate the issue.
The component can be installed/uninstalled/updated separately. Setup is located on VS DVD in WCU\WebToolsCore folder. If you accidentally uninstalled the component, you can simply run WebToolsCore.exe from the abovementioned folder. The setup does not have UI, simply give it about 5-10 minutes to complete.
An old question, but I bumped into it this week and want to post Microsoft's suggested solution.
ROOT CAUSE
The root cause of this problem is that Office 2007 and the VS 2008 web designer both share a component, 32-bit MSXML5. When Office 2007 uninstalls or gets upgraded, MSXML5 is removed yet Visual Studio still needs it.
WORKAROUND
Workaround if you manually uninstalled Office 2007 AND have a non-Express version of VS 2008. Uninstall and then reinstall “Microsoft Visual Studio Web Authoring Component“. Next run WCU\WebDesignerCore\WebDesignerCore.exe from the install disk.
For more information see MS article:
Upgrade or Uninstall of Office 2007 might cause VS 2008 Web designer to hang
If you don't use the ClearCase plugin do you still get the problem?
i.e. Try saving copying your solution to your local machine, remove all the source control bindings and see if you get the same problem.
Depending on how your environment is set up, you could be looking at a lag when VB is communicating with ClearCase.
And if all else fails, there are a few good diagnostic tools from the old SysInternal suite to help you figure out if it is a file access, registry or network problem.
SysInternals Site
FileMon - File reads / writes
RegMon - Registry reads / writes
TCPView - Network traffic