From Microsoft Connect:
Until Microsoft come up with an official solution there is a working workaround for this problem.
This problem only appears to affect people who have not got Visual C++ Installed.
1.) Download VS90SP1-KB971092-x86.exe from here …
2.) Start the installation VS90SP1-KB971092-x86.exe
3.) Wait for the error message to come up – DO NOT CLOSE THE WINDOW!
4.) Copy the temp. folder where the patch has been unpacked to a new folder, for example onto your desktop.
5.) Close VS90SP1-KB971092-x86.exe that you started in 2.)
6.) Navigate to <drive>:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools and find vsvars32.bat.
7.) Change the permissions on the file to allow everyone to edit it.
8.) Start VS90SP1-KB971092-x86.msp from within the saved folder and the process should complete.
Great tips on how to speed up Visual Studio 2008! Combine this with the hotfix and SP1, and…it’s almost as fast as Visual Studio 2005. 😉
- Turn off validation
- Turn off the Navigation Bar
- Show Live Semantic Errors
- Track changes
- Animate environment tools
- Compile for the correct platform
- Speed up debugging by removing breakpoints
- Formatting XML for easy diff
Find out all the details at the original post: Speed up Visual Studio – EPiServer Labs.
This is just awesome – with Ctrl+I, you can perform a type-ahead search within Visual Studio, just like Firefox!
Again, my buddy Sairama to the rescue. Just when I think I’ve pretty much got VS.NET down solid (only being use it since Pre-Beta days, right?) I’m thrown a curve ball called incremental search. I guess I just assumed that a feature that was so cool in so many other editors would never make it into VS.NET. Silly me.
So, lest I be the most ignorant, fire up Visual Studio.NET, get some code in there, hit Ctrl-I and start typing. After you’ve found something, use F3 to Find Next. In the words of Chris Sells – It’s pure sex.
via Scott Hanselman’s Computer Zen – My ignorance proceeds me: Visual Studio.NET Incremental Search.
I’ve seen a *lot* of hits on my post “Visual Studio 2008 Is Pretty Damn Slow…“, which means that a lot of you are probably still experiencing speed issues with Visual Studio 2008. In regard to this, I thought it might be prudent to post information about the recently released Service Pack 1 for VS2008 and where to find it:
Visual Studio 2008 SP1 and .NET Framework 3.5 SP1 significantly improve the developer experience during the development process, and at runtime. These improvements address top issues reported by customers. For more information, see Visual Studio 2008 SP1 and .NET Framework 3.5 SP1.
Additionally, the original hotfix which was intended to fix the speed issue (and is probably integrated into VS2008SP1) is available here:
Here are all my posts related to this Visual Studio 2008:
Here’s a MSDN forum article that links back to my post about the VS2008 hotfix:
I believe there are known issues with VS2008 and web development. This article contains a link to some hotfixes for VS2008 web development. Maybe it’ll fix your problem: https://blog.wolffmyren.com/2008/02/11/performance-and-editor-fixes-for-vs2008/
Great post on how to share a solution between VS2008 and VS2005, from stevenharman.net/blog:
One of the things I’m most excited about with Visual Studio 2008 is it’s ability to target various versions of the .net framework, a feature known as multi-targeting.
I recently rebuilt a (hand-me-down) laptop for use at developer group meetings, conferences, and coding from the couch. When building out the machine I decided to only install VS2008 and make use of multi-targeting to work on my various .net 2.0 projects… like Subtext. Today I finally got around to loading Subtext up in VS2008 and I was expecting some heartache.
But I did a little research first and luckily came across Rick’s great post explaining how VS2008 and VS2005 can be made to play nice together, allowing you to work with your projects in either IDE. The gist is, the project files (i.e.- your
.csproj files) will work in either environment, but you’ll need to maintain separate solution files. Not a huge deal as most of the churn is usually in the individual project files, and not the solution.
(via Multi-Targeting VS2005 and VS2008 Web Application Projects, a Gotcha!)
In regard to my previous post, Visual Studio 2008 Is Pretty Damn Slow, a couple engineers from Microsoft have contacted me to let me know that a hotfix has been made public which should address the performance issues I mentioned in that previous post.
The blog entry regarding this hotfix can be found here:
Downloadable Hotfix: Performance and Editor fixes for Microsoft Visual Studio 2008 and Visual Web Developer Express 2008
More info from Scott Guthrie’s Blog:
VS 2008 Web Development Hot-Fix Roll-Up Available
More info from Rick Stahl’s Blog:
Visual Studio Hotfix for Slow Web Forms Editing and Input Focus Issues
And the hotfix itself, here:
Quote from the MSDN blog linked above (Downloadable Hotfix…):
Shortly after I posted my last entry (Visual 2008…) and left a comment on this blog, two programmers from Microsoft left comments offering assistance in troubleshooting the speed issues with Visual Studio 2008.
Much thanks to David and Jason from Microsoft!