 |
|||||||||
|
|||||||||
|
|
---------------
---------------
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.
I found it to take a long time myself, but it improved VS for me. It was
very unstable before applying SP1. Also, I only have 512 meg of memory.
The install only took at maximum around 110 megs or so. They must scale
the install to match the machine or something. I found memory was not an
issue, only the time it took. It took maybe 2 hours or so to install.
The install was a nightmare, but my .NET 3 stuff seems ok at this point.
I'm using the beta version of Expression Blend for my forms though, which
seems much more suited for the task at this point.
Thanks for that feedback Phil. That is a definite plus for those running
less memory!!!
took time but made Studio lot lot more stable and no proplemo with .net 3.
Another issue is:
