VS 2005 SP1

Hi,
Any one done the SP1 install yet? Heard it was very long and caused some problems. I was wondering if the SP intsallation has effected any development projects of those using DASP. Anything to look out for during the install, or after? Thanks, BRN..

 

The SP does take a long time but it is well worth it, awesome update with tons of new changes including Ajax support.
Read the docs first, one change you will need to make is removing the project add-in which is no longer needed but that's covered in the readme.

 

Hi,
Thank you for the info. The part about removing the project add-in is good to know - as it's the kind of stuff that can get missed if the readme file has a lot of stuff (which I'm guessing is the case). As it sounds like a lot of good stuff for the time/effort, I'll try the install when I know I can afford the time to watch it chug away. BRN..

 

Scott Guthrie did a very good blog about the SP and in it he also put a strong emphasis on:


1)Before starting the SP1 upgrade make sure you first uninstall the standalone VS 2005 Web Application Project download if you've installed that on your system. You'll no longer need this as support for it is built-in to SP1, and the SP1 installer will block and make you uninstall it if you have it installed. Your existing web application project files will continue to work just fine- so you won't need to-do anything toupdate them to work with SP1.


http://weblogs.asp.net/scottgu/archive/2006/12/15/visual-studio-2005-service-pack-1-sp1-released.aspx

 

There is a bug in windows 2003 which prevents installation from completing so before you install the SP on a windows 2003 machine make sure to follow the following steps. I found this soultion onScott Guthrie Blog. It resolved the instillation error...

If you extract the .exe file and see the properties on the .msp file under 'Digital Signatures' you will see that the signature/certificate is not valid.

1) Open local security setting: Start -> Programs -> Administrative Tools -> Local Security Policy.

2) Click on 'Software Restriction Policies' and if it shows 'No Software Restriction Policies Defined' then insert a new (right click the left pane node).

3) 2 x click on the 'Enforcement' entry and under 'Apply software restriction policies to the following users:' section change to 'All users except local administrators'.

4) reboot

kevinasp.com

 

Hi,
Thanks for the reply and info. As it happens, I didn't see this reply intil after I did the SP1 install on my dev machine; so I did not do the steps recommended in the reply. None the less, the install went through without incident. The total time for installation was about 1/2 hour. The only user interaction windows I saw were for procedding with the install, and to accept the EULA. Other than those, it was just a matter of letting it run.
As to why it did work - inspite of not doing the adjustments you mentioned - I can only guess. For one thing, the computer mentioned has the R2 version of WS2K3. Also, I did the SP download just before the install, so it may have been updateed to cover the fault. I did remove the Web distribution Projects add-in before installing SP1 (BTW, I would have removed the Web App Projects add-in, but it wasn't listed as a seperate component), and took the usual steps of defraging the drives, and logging on as sys admin for that machine. It may matter also, that my configuration for VS 2005 is pretty basic: VB, J#, VWD, and a custom tool for data modeling called NORMA. It's the Standard Edition, so if the fault is caused by Team Services, etc..., I wouldn't have been effected.
The About listings under the Help menu item show that the correct upgrades are in place. In all, the install was easier than I expected. Hope others fair as well. Thanks again. I'll keep you post in mind if I see others getting stuck with problems on the SP intallation. BRN..