Microsoft Visual Studio 2005 Service Pack 1 a 6.2+ Gig Update????
Why in the heck is a service pack a 6.2+ Gig, several hour update??? WOW!!!!!
My install took 2 hours (4.5 hours total with the attempted repairs- see "Was the install worth it?"- below) and used up 2.6 Gig. So I assume the 6.2 Gig can happen if you have the Tester, Database, and TFS VSTS tools installed.
At the beginning of the installation processes, the install processes consumed more that 1 Gig of memory, probably around 1.3 Gig. Then it settled down to 600M most of the time, but went back up over 1G during each install.
I wouldn't attempt this install with less than 2 Gig of memory.
I have VSTS 2005 premier partner installed, which gets its own update, as well as Architect and Developer installed. They each got their own update too.
I have a virtual instance that has all of VSTS 2005 and TFS, I think I will install that over night, or maybe never. The installation process stops along the way and you have to accept the licensing agreement for each installation. So you can't just start it and let it run through.
At this rate we will all soon be carrying desktops around instead of laptops.
Was the install worth it?????????????????????
Well it does build big solutions faster, but all my .NET 3.0 stuff was completely trashed (WWF, WCF, & WPF). After attempting repairs, uninstalls, and reinstalls, most of the WPF xaml that displayed in the designer previous to the install, now errors out.
Will I install it on my other dev boxes? NOPE. Not until I have an absolute need to. The only one I may install it on is the virtual instance I mention above, and that is because I am evaluating TFS for my company and it may improve some of the performance and features. WCF, WWF, and WPF are not on that install. I am evaluating them on a different box. If they were, I wouldn't do it.
Over all I give the experience two thumbs down, and do not recommend it, especially if you want to use the .NET 3.0 tools.
Well have fun if you decide to suffer the install... you can get it from links found here.
My install took 2 hours (4.5 hours total with the attempted repairs- see "Was the install worth it?"- below) and used up 2.6 Gig. So I assume the 6.2 Gig can happen if you have the Tester, Database, and TFS VSTS tools installed.
At the beginning of the installation processes, the install processes consumed more that 1 Gig of memory, probably around 1.3 Gig. Then it settled down to 600M most of the time, but went back up over 1G during each install.
I wouldn't attempt this install with less than 2 Gig of memory.
I have VSTS 2005 premier partner installed, which gets its own update, as well as Architect and Developer installed. They each got their own update too.
I have a virtual instance that has all of VSTS 2005 and TFS, I think I will install that over night, or maybe never. The installation process stops along the way and you have to accept the licensing agreement for each installation. So you can't just start it and let it run through.
At this rate we will all soon be carrying desktops around instead of laptops.
Was the install worth it?????????????????????
Well it does build big solutions faster, but all my .NET 3.0 stuff was completely trashed (WWF, WCF, & WPF). After attempting repairs, uninstalls, and reinstalls, most of the WPF xaml that displayed in the designer previous to the install, now errors out.
Will I install it on my other dev boxes? NOPE. Not until I have an absolute need to. The only one I may install it on is the virtual instance I mention above, and that is because I am evaluating TFS for my company and it may improve some of the performance and features. WCF, WWF, and WPF are not on that install. I am evaluating them on a different box. If they were, I wouldn't do it.
Over all I give the experience two thumbs down, and do not recommend it, especially if you want to use the .NET 3.0 tools.
Well have fun if you decide to suffer the install... you can get it from links found here.
posted by tadanderson at 11:19 AM
1 Comments:
Another issue is:
"Unexpected error encountered. It is recommended that you restart the application as soon as possible.".
- Error : unspecified error
- File : vsee\pkgs\vssprovider\abstractionlayerdispatcher.cpp
- Line number : 4701.
After installing the service pack, VSS bindings to sites in IIS do not work. You get the above error. I have had to change all mine to work through the file system, which is aggravating in debug, because you have to manually attach to IIS every time.
I can't run the VS web site because of ports changing, and this is a smart client app.
Post a Comment
<< Home