I few months back, I was having major problems with VS 2008 crashing on me left and right.  After trying numerous things to resolve my problem, I finally decided to uninstall all of the .Net Frameworks and VS, then reinstall.  My problems started shortly after I installed SP1 (both .Net Framework and VS 2008). 

I can’t say for certain that SP1 was causing my problems, but since then (after reinstalling without the service packs), I have not experienced the crashing.

There are other reasons that I wanted to skip SP1, many of which are documented by Microsoft themselves.  Not the least of these was the issue regarding transactions in Oracle.  That issue, as well as many others, has been since resolved.

I’ve been taking this week to do some technical research on tools and frameworks we might want to use on our next project.  One of those tools is ASP.Net MVC.  It turns out that the installer requires .Net 3.5 SP1, and to deploy MVC requires a couple of libraries from the service pack.  I also wanted to evaluate Microsoft’s chart controls, which also requires SP1.

So with much hesitation I decided to install SP1 once more.  Since VS was where I experienced so many problems, I only installed SP1 for the framework, and not VS.


Well, almost immediately I was discouraged by the this error.  Choosing Ignore didn’t seem to hurt anything.

So far, a few days after the install of SP1, I have had not experienced the same issues as before.  I’m still very hesitant to install VS SP1.

Funny thing is, I decided not to evaluate MVC beyond some internet research.  So, one reason to install SP1 fell to the wayside.


posted on Wednesday, April 1, 2009 3:35 PM


# re: Installing SP1… again
posted by Sandeep
on 4/8/2009 11:06 AM
SP1 with TFC caused a host of issues for me as well. The sequence (if you ever decide to install SP1 for VS) should be VS, TFC and then SP1

Post A Comment