logo

 

     
 
Home
Site Map
Search
 
:: Bitwise Courses ::
 
Bitwise Dusty Archives
 
 
 

rss

 
 

ruby in steel

learn aikido in north devon

Learn Aikido in North Devon

 


Section :: Bytegeist

- Format For Printing...

Visual Studio SP1 woes

If it ain’t broke don’t fix it
Saturday 23 December 2006.
 

“It’s better to have known bugs rather than unknown fixes”. It’s a motto that’s served me well over the years, and it applies particularly to software ‘fix packs’ or ‘service packs’. Well, I broke the rule yesterday and installed Visual Studio SP1. And I’m now re-installing Visual Studio from scratch as I write this. It’s nobody’s fault but mine, and, yes, Microsoft’s.

The problem I’ve got is that the debugger no longer functions as it once did. I used to be able to hover over a variable and ‘drill down’ into it. Now I get the message “Function evaluation disabled because a previous function evaluation timed out” all over the place and once I step with F10, Visual Studio disappears into a black hole, from which I can’t recover. Whatever the cause (these are pretty complicated variables: generic lists of dictionaries of sorted lists – that sort of thing), this did NOT happen with the original Visual Studio installation. Unfortunately, this is vital for my debugging and I can’t really live without it. So bye-bye SP1.

That’s not the only problem with SP1. I started installing it at lunchtime yesterday. I was still at it in the evening. Not only is SP1 vast – over 440MB – its installation is primitive. I was asked three times if I wanted to install a particular product at different stages in the installation. Of course, I’d gone out for a walk, painted the house, watched the paint dry in the meantime and not realised that SP1 was waiting for an answer. I’d have thought that it might have been an idea to present a summary screen at the start of the process and go from there. Apparently not. Even so, each stage seems to count the bits on your hard disk and then cross-checks the result. What on earth was it doing? Beats me.

Further, the SP1 installation process lies. It has a cheery little progress bar giving the expected time to complete the installation. I happily sat and watched it report zero minutes to completion. For over half-an-hour. More than once, more fool me.

I’m reluctant to throw rocks at Microsoft’s Visual Studio developers. I’ll be in a similar situation shortly – we’re releasing a Ruby IDE Ruby In Steel soon and I’m pretty sure I’ll have let some bloopers out of the door in the process. It’s just the nature of software.

Still, it doesn’t stop me feeling annoyed with Microsoft. At the end of this little saga, I’ll have wasted the best part of a day from my precious release schedule with nothing to show for it.

But the person I’m most annoyed with is myself. For breaking the golden rule: “if it ain’t broke – don’t fix it”.

Bah. Humbug. Merry Christmas to one and all.

AddThis Social Bookmark Button

Forum

  • Visual Studio SP1 woes
    28 October 2007

    Yeah! Happened with me too. Looks like whatever productivity gains offered by SP1 gets lost with the time it takes to install it. Looks like MS fired all their QA guys and is using ’cheap’ QA services of community. It took me overnight to install it and in the morning i get a shock when I saw a crazy dialog asking me if I’m sure if I want to install this crap. Obviously I said no and threw the SP1 disk into the trash. I’ll wait for sp2 instead...

  • Visual Studio SP1 woes
    4 March 2007, by ian marteens

    I also had problems installing VS2k5 SP1: it refuses to install! However, it must have done something to my laptop, since now I’m having a lot of trouble with the debugger. My original plan was to reformat the machine (there must be some files from the beta here and there) and reinstall both VS and the SP1... but now I have doubts about the SP1 part.

  • Visual Studio SP1 woes
    23 December 2006, by An Observer

    Isn’t SP1 supposed to (among other things) lay the groundwork for a subsequent Vista fix to make the debugger function in that new, more secure environment?

    Perhaps the problems lie in the reworking that was done for Vista but didn’t entirely make it into SP1?


Home