regret for upgrade to VS2005
-
Hi, I just upgrade the VS2003 to VS2005. But I found that the project building time almost doubles as in VS2003. And it caused much interrupts in development work ! Any tricks to improve this situation besides upgrade to a faster PC ? Thanks
Reinstall VS 2003. This statement is false.
-
Hi, I just upgrade the VS2003 to VS2005. But I found that the project building time almost doubles as in VS2003. And it caused much interrupts in development work ! Any tricks to improve this situation besides upgrade to a faster PC ? Thanks
Kim0618 wrote:
Any tricks to improve this situation besides upgrade to a faster PC ?
Wait for the service pack? :~ Jeremy Falcon
-
Hi, I just upgrade the VS2003 to VS2005. But I found that the project building time almost doubles as in VS2003. And it caused much interrupts in development work ! Any tricks to improve this situation besides upgrade to a faster PC ? Thanks
There's an MS KB article out there somewhere which illustrates a mystical magical dance you can perform to make VS2005 run like a Cheetah. If only I could find the link... Ah yes, here[^] it is. Best of luck. :-D :josh: My WPF Blog[^]
-
There's an MS KB article out there somewhere which illustrates a mystical magical dance you can perform to make VS2005 run like a Cheetah. If only I could find the link... Ah yes, here[^] it is. Best of luck. :-D :josh: My WPF Blog[^]
Hehe. I think those of us who load it up with CTP bits experience said dance far more often than others. ;)
225 years ago, we set an example for the rest of the world by creating a country where everyone could vote...
Well, except for women and black people, but we fixed that!
-Adam Duritz, of Counting Crows -
Hehe. I think those of us who load it up with CTP bits experience said dance far more often than others. ;)
225 years ago, we set an example for the rest of the world by creating a country where everyone could vote...
Well, except for women and black people, but we fixed that!
-Adam Duritz, of Counting CrowsDavid Stone wrote:
I think those of us who load it up with CTP bits experience said dance far more often than others.
Damn right! I feel like my study at home has transformed into a dance club (actually, more a mosh pit). :jig: :josh: My WPF Blog[^]
-
David Stone wrote:
I think those of us who load it up with CTP bits experience said dance far more often than others.
Damn right! I feel like my study at home has transformed into a dance club (actually, more a mosh pit). :jig: :josh: My WPF Blog[^]
Right.... My solution was to buy a new computer, with two Xeon MP 2.8GHz 800 FSB CPU's and 2GB of memory. ;P Well not entirely for VS2005, I also had problems running the many test situations for my middleware projects :laugh: WM.
What about weapons of mass-construction? -
Right.... My solution was to buy a new computer, with two Xeon MP 2.8GHz 800 FSB CPU's and 2GB of memory. ;P Well not entirely for VS2005, I also had problems running the many test situations for my middleware projects :laugh: WM.
What about weapons of mass-construction?WillemM wrote:
My solution was to buy a new computer, with two Xeon MP 2.8GHz 800 FSB CPU's and 2GB of memory.
Good solution! I would have gone for 4GB, but that's me. A friend of mine just got a machine with 4 GB of RAM...whoa baby, that thing burns! :cool: :josh: My WPF Blog[^]
-
Hi, I just upgrade the VS2003 to VS2005. But I found that the project building time almost doubles as in VS2003. And it caused much interrupts in development work ! Any tricks to improve this situation besides upgrade to a faster PC ? Thanks
I believe a slapfest in order for the architects and developers of VS2005. Here is my experience. Let’s start from install. I decided to build a test machine to experiment with VS2005. The machine is nothing extra ordinary, a 2 GHz CPU, 1 GB of memory and a sixty GB hard drive partitioned as C and D. I typically move “MyDocument” to D just in case if OS partition is toast I can at least get to my files. After installing the OS from my MSDN CD, fed the Visual Studio to the machine. It complained that I need to have XP SP2. Hmm… where is that freaking CD in the MSDN subscription? After half an hour of searching sorting, it turned out that I don’t have the CD because XP SP2 CD was shipped after my subscription ran out. I guess time to go to Windows Update… nice page layout…, machine is scanned and later announced that before I can proceed to update my windows; I need to upgrade my Windows Installer. I am thinking What!?.. Some bits are downloaded (I have no idea what) and the disk starts churning. Few minutes later a message box pops up that I need to reboot my machine… The plot is starting to turn into a bad Mexican porno… Back to explorer and windows update site. After more scanning the system announced that I have to download 47 critical updates, and few non critical ones. The load is going to cost me an hour and about 1 gig of disk space. More voices in my head… what the heck was that crap I installed from the CD then. Two hour and several reboots later, I tend the machine again, apparently with all the critical updates. Let’s take a shot at that Visual Studio 2005 CD one more time. “Click to begin…” more disk churning and I am told that this software will be installed in 70 steps (do I care). I did not bother to change any install options and stuck with all defaults. The clock is ticking but is that progress bar progressing? An hour and 20 minutes later, a man with a perfect smile tells me that all is well. The install wizard pops up again telling me that all the things I have installed so far does not include any Help and I need to pony up another gig and an hour of my time to install the help. Another hour goes by and I finally get the documentation. Time to fire up this beast…. More hard drive churning but nothing is happening… Oh it is updating help. Finally, it is up and running…. Oh shit forgot to install IIS on this machine. Back to Add Remove Program applet. Few minutes later I have the IIS up and running. Back to VS2005, Let’s try to compile an
-
I believe a slapfest in order for the architects and developers of VS2005. Here is my experience. Let’s start from install. I decided to build a test machine to experiment with VS2005. The machine is nothing extra ordinary, a 2 GHz CPU, 1 GB of memory and a sixty GB hard drive partitioned as C and D. I typically move “MyDocument” to D just in case if OS partition is toast I can at least get to my files. After installing the OS from my MSDN CD, fed the Visual Studio to the machine. It complained that I need to have XP SP2. Hmm… where is that freaking CD in the MSDN subscription? After half an hour of searching sorting, it turned out that I don’t have the CD because XP SP2 CD was shipped after my subscription ran out. I guess time to go to Windows Update… nice page layout…, machine is scanned and later announced that before I can proceed to update my windows; I need to upgrade my Windows Installer. I am thinking What!?.. Some bits are downloaded (I have no idea what) and the disk starts churning. Few minutes later a message box pops up that I need to reboot my machine… The plot is starting to turn into a bad Mexican porno… Back to explorer and windows update site. After more scanning the system announced that I have to download 47 critical updates, and few non critical ones. The load is going to cost me an hour and about 1 gig of disk space. More voices in my head… what the heck was that crap I installed from the CD then. Two hour and several reboots later, I tend the machine again, apparently with all the critical updates. Let’s take a shot at that Visual Studio 2005 CD one more time. “Click to begin…” more disk churning and I am told that this software will be installed in 70 steps (do I care). I did not bother to change any install options and stuck with all defaults. The clock is ticking but is that progress bar progressing? An hour and 20 minutes later, a man with a perfect smile tells me that all is well. The install wizard pops up again telling me that all the things I have installed so far does not include any Help and I need to pony up another gig and an hour of my time to install the help. Another hour goes by and I finally get the documentation. Time to fire up this beast…. More hard drive churning but nothing is happening… Oh it is updating help. Finally, it is up and running…. Oh shit forgot to install IIS on this machine. Back to Add Remove Program applet. Few minutes later I have the IIS up and running. Back to VS2005, Let’s try to compile an
mango_lier wrote:
The plot is starting to turn into a bad Mexican porno…
:omg: Are you saying that there are good ones?! Dios mio! :josh: My WPF Blog[^]
-
I believe a slapfest in order for the architects and developers of VS2005. Here is my experience. Let’s start from install. I decided to build a test machine to experiment with VS2005. The machine is nothing extra ordinary, a 2 GHz CPU, 1 GB of memory and a sixty GB hard drive partitioned as C and D. I typically move “MyDocument” to D just in case if OS partition is toast I can at least get to my files. After installing the OS from my MSDN CD, fed the Visual Studio to the machine. It complained that I need to have XP SP2. Hmm… where is that freaking CD in the MSDN subscription? After half an hour of searching sorting, it turned out that I don’t have the CD because XP SP2 CD was shipped after my subscription ran out. I guess time to go to Windows Update… nice page layout…, machine is scanned and later announced that before I can proceed to update my windows; I need to upgrade my Windows Installer. I am thinking What!?.. Some bits are downloaded (I have no idea what) and the disk starts churning. Few minutes later a message box pops up that I need to reboot my machine… The plot is starting to turn into a bad Mexican porno… Back to explorer and windows update site. After more scanning the system announced that I have to download 47 critical updates, and few non critical ones. The load is going to cost me an hour and about 1 gig of disk space. More voices in my head… what the heck was that crap I installed from the CD then. Two hour and several reboots later, I tend the machine again, apparently with all the critical updates. Let’s take a shot at that Visual Studio 2005 CD one more time. “Click to begin…” more disk churning and I am told that this software will be installed in 70 steps (do I care). I did not bother to change any install options and stuck with all defaults. The clock is ticking but is that progress bar progressing? An hour and 20 minutes later, a man with a perfect smile tells me that all is well. The install wizard pops up again telling me that all the things I have installed so far does not include any Help and I need to pony up another gig and an hour of my time to install the help. Another hour goes by and I finally get the documentation. Time to fire up this beast…. More hard drive churning but nothing is happening… Oh it is updating help. Finally, it is up and running…. Oh shit forgot to install IIS on this machine. Back to Add Remove Program applet. Few minutes later I have the IIS up and running. Back to VS2005, Let’s try to compile an
You should have been about to just run aspnet_regiis.exe to register the new version of .NET with IIS. Steve Maier, MCSD MCAD MCTS
-
You should have been about to just run aspnet_regiis.exe to register the new version of .NET with IIS. Steve Maier, MCSD MCAD MCTS
Thanks for the tip I tried it with no success, if the IIS is installed after installing the .Net runtime, aspnet_regiis -i or aspnet_regiis -lru will not work. Repair does not do the trick either. The only viable solution is uninstall and reinstall the runtime. But that was not the point of the rant:) -- modified at 14:11 Tuesday 18th July, 2006
-
Hi, I just upgrade the VS2003 to VS2005. But I found that the project building time almost doubles as in VS2003. And it caused much interrupts in development work ! Any tricks to improve this situation besides upgrade to a faster PC ? Thanks
Kim0618 wrote:
Any tricks to improve this situation besides upgrade to a faster PC ?
Write less code? Marc XPressTier
Some people believe what the bible says. Literally. At least [with Wikipedia] you have the chance to correct the wiki -- Jörgen Sigvardsson
People are just notoriously impossible. --DavidCrow
-
Kim0618 wrote:
Any tricks to improve this situation besides upgrade to a faster PC ?
Write less code? Marc XPressTier
Some people believe what the bible says. Literally. At least [with Wikipedia] you have the chance to correct the wiki -- Jörgen Sigvardsson
People are just notoriously impossible. --DavidCrow
Glad to see you finally "finished" the AAL, Marc. :)
225 years ago, we set an example for the rest of the world by creating a country where everyone could vote...
Well, except for women and black people, but we fixed that!
-Adam Duritz, of Counting Crows -
Kim0618 wrote:
Any tricks to improve this situation besides upgrade to a faster PC ?
Write less code? Marc XPressTier
Some people believe what the bible says. Literally. At least [with Wikipedia] you have the chance to correct the wiki -- Jörgen Sigvardsson
People are just notoriously impossible. --DavidCrow
Marc Clifton wrote:
Write less code?
Or you could just not compile as often. :laugh: :josh: My WPF Blog[^]
-
Hi, I just upgrade the VS2003 to VS2005. But I found that the project building time almost doubles as in VS2003. And it caused much interrupts in development work ! Any tricks to improve this situation besides upgrade to a faster PC ? Thanks
Kim0618 wrote:
Any tricks to improve this situation besides upgrade to a faster PC ?
tryremovingallwhitespaceinyourcode Do the chickens have large talons?
-
Glad to see you finally "finished" the AAL, Marc. :)
225 years ago, we set an example for the rest of the world by creating a country where everyone could vote...
Well, except for women and black people, but we fixed that!
-Adam Duritz, of Counting CrowsDavid Stone wrote:
Glad to see you finally "finished" the AAL,
Hey, you noticed! :jig: Marc XPressTier
Some people believe what the bible says. Literally. At least [with Wikipedia] you have the chance to correct the wiki -- Jörgen Sigvardsson
People are just notoriously impossible. --DavidCrow
-
Hi, I just upgrade the VS2003 to VS2005. But I found that the project building time almost doubles as in VS2003. And it caused much interrupts in development work ! Any tricks to improve this situation besides upgrade to a faster PC ? Thanks
take the battery out of your watch? this way VS2005 will compile even the biggest projects in no time at all! :-D or you could just kill the evil that is the C++ intellisense scanner for VS2005, which will free up several billion CPU cycles. of course doing this will break all sorts of things, and means you will need something else to provide you with intellisense, but still, this is what i do :)
zen is the art of being at one with the two'ness
-
Kim0618 wrote:
Any tricks to improve this situation besides upgrade to a faster PC ?
tryremovingallwhitespaceinyourcode Do the chickens have large talons?
plus, remember to reduce the font size a couple of points, and switch to a proportional font as well :)
zen is the art of being at one with the two'ness
-
I believe a slapfest in order for the architects and developers of VS2005. Here is my experience. Let’s start from install. I decided to build a test machine to experiment with VS2005. The machine is nothing extra ordinary, a 2 GHz CPU, 1 GB of memory and a sixty GB hard drive partitioned as C and D. I typically move “MyDocument” to D just in case if OS partition is toast I can at least get to my files. After installing the OS from my MSDN CD, fed the Visual Studio to the machine. It complained that I need to have XP SP2. Hmm… where is that freaking CD in the MSDN subscription? After half an hour of searching sorting, it turned out that I don’t have the CD because XP SP2 CD was shipped after my subscription ran out. I guess time to go to Windows Update… nice page layout…, machine is scanned and later announced that before I can proceed to update my windows; I need to upgrade my Windows Installer. I am thinking What!?.. Some bits are downloaded (I have no idea what) and the disk starts churning. Few minutes later a message box pops up that I need to reboot my machine… The plot is starting to turn into a bad Mexican porno… Back to explorer and windows update site. After more scanning the system announced that I have to download 47 critical updates, and few non critical ones. The load is going to cost me an hour and about 1 gig of disk space. More voices in my head… what the heck was that crap I installed from the CD then. Two hour and several reboots later, I tend the machine again, apparently with all the critical updates. Let’s take a shot at that Visual Studio 2005 CD one more time. “Click to begin…” more disk churning and I am told that this software will be installed in 70 steps (do I care). I did not bother to change any install options and stuck with all defaults. The clock is ticking but is that progress bar progressing? An hour and 20 minutes later, a man with a perfect smile tells me that all is well. The install wizard pops up again telling me that all the things I have installed so far does not include any Help and I need to pony up another gig and an hour of my time to install the help. Another hour goes by and I finally get the documentation. Time to fire up this beast…. More hard drive churning but nothing is happening… Oh it is updating help. Finally, it is up and running…. Oh shit forgot to install IIS on this machine. Back to Add Remove Program applet. Few minutes later I have the IIS up and running. Back to VS2005, Let’s try to compile an
At least XP SP2 didn't render your machine ubootable like it did mine 18 months ago! It did take me 4 days to install VS 2003 three years ago though! VS 2005 was a doddle by comparison. One of the worst things about MS apps. are the interdependencies and the tendency to force you to have the latest versions of all their complementary software. Kevin
