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.
Cool post with a lot of great history and font samples!
As a self proclaimed programmer/designer I enjoy not only the logical and practical things in life, but also the beautiful and well designed. And I find the greatest pleasure when these things converge to produce something extraordinary.One such thing is Typography. Typography is the art of language, the visualization of the spoken word. A medium by which non-verbal communication is made possible. And though I profess no expertise in this art, I have come to deeply appreciate it’s power and ability to convey the same message in so many different ways. Each with a unique feeling and style.
In 1956 Howard Kettler designed the typeface Courier. It was made for IBM’s new (and revolutionary) line of electric typewriters. Originally called “Messenger”, Courier is one of the earliest fixed-pitch (also known as Monospace) fonts, meaning each character takes up the same amount of space on a line; allowing for easy tabular alignment and legibility.
Courier was a hit, and as many made the transition from typewriter to computer, this classic typeface wasn’t far behind. It was included in all early Apple computers, and while creating the core fonts for Windows 3.1, Microsoft hired Monotype Typography to give Courier a makeover. And so Courier New was born, as a thinner and cleaner version of it’s former self.
via the hamstu » The Typography of Code.
While coding in Java recently, I decided to do a little research to see if Java supported the #region directive (or something similar) and found a ton of articles knocking its usage as poor programming style.
Personally, I love the #region directive in C#, as it allows me to keep my code more organized (and yes, I am aware of the exisiting code-folding functionality in Visual Studio). In the files I work with, I’ve become pretty meticulous about organizing the code blocks into regions, partially because I like the organization, and partly because I was previously under the impression that it was good form to keep source files organized in this way. I use the following regions myself, generally:
- Private/Protected Members
- Public Accessors
- Public Methods
- Protected Methods
- Private Methods
- (Anything class specific)
I agree with the sentiment in the articles I’ve read that it is *not* good practice to sweep bad code under the rug by hiding it from the developer in a folded #region, but I think that organizing relatively good code into regions like the ones I’ve mentioned above makes it a lot easier to get directly to the code I want to work on.
What do you think? I’m curious to see justifications for/against this directive, and as always, thanks for reading!
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.
Woo-hoo! Another milestone!
Special thanks to the post Visual Studio 2008 Is Pretty Damn Slow… for giving me over 7,000 hits on its own! (Seems that people are still searching pretty heavily for Visual Studio 2008 being slow and how to fix it…)
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:
Heh. I’m feelin’ quite nice about that one. 😉
Here’s the post from the search result, btw:
Visual Studio 2008 Is Pretty Damn Slow…