Hi,

  Having looked a few of the posts from those that have installed (or tried), Visual Studio SP1.  I can see that it's not trivial.  Would those that have gone through the process plese tell us what they would do differently, if they were going to do the install - now that they are wiser?  Are there things they'd do first, skip, put off, etc...?  Please let us know which features/changes that SP1 has provided that make the process worthwhile.  Would they do the install, if they knew what they were going to get, and what they were getting into?  Like the guy from Stripes "If we get into some tough combat - I'll be right behind you guys."  Thanks  BRN..
 

Changes in Web Tools are listed here:

http://blogs.msdn.com/webdevtools/archive/2006/12/20/visual-studio-2005-sp1-released-details-on-changes-for-web-tools.aspx

I'll tell you what happened to me and let you decide what you want to do...

I had converted a VS 2003 project to VS 2005 using the original release version of VS 2005.  There were some conversion issues, but aren't there always!  So I resolved all of the issues, ok.  Some time later I upgraded another machine to VS 2005 SP1.  Well, when I opened the previously converted project on the other machine, the VS Conversion wizard popped up and converted it all over again!  Now I've got a whole slew of NEW issues.  I've gone round and round with this and have just now figued out that it must be SP1!  If I could do it all over again, I don't think I would have installed SP1!

 Hi,

I think your comment points out a fact about software upgrades/conversions/modifications in general, when they concern the development environment for applications that are in production, or are otherwise valuable.  Having gotten burned myself in similar circumstances, your comment is a reminder to preserve important projects/applications in the form that works.  Don't assume that a later version or upgrade to the IDE can only make things better - or that you can always undo the conversion to get back to where when things worked right.  Also don't assume that an update or upgrade wouldn't do any conversion you don't intend.  Even if the new version is polite enough to ask you whether you really, really want to convert the application, and even if it warns you about possible consequences, all that may get lost in the blur of warnings, options and general information overload.

Maybe the lesson is to always take steps to preserve a working copy of your application.  It's probably best that the archived copy be somewhere untouchable by the IDE - in case it does you the favor of converting all the files of a given file type that it can find; so don't let it find your archive.

BRN..