Visual Studio 2008 upgrade

Visual Studio 2008 review - Team ExplorerWell this will be a short one………………. it’s very disappointing.

  • You can’t CTRL+F or CTRL+SHIFT+F will crash the IDE.
  • Editing any CSS file will crash your IDE….ANY CSS file.
  • Teeam explorer’s ‘Queue New Build’ doesn’t queue them at all. It’s the exact same as it used to be (see screenshot below).
  • It’s slow even on a dual core XEON with 4GB Ram

In conclusion - don’t bother upgrading, even if you do get javascript autocompletion.

7 Comments

  1. Posted January 22, 2008 at 10:36 am | Permalink

    oo, nasty. Perhaps they ought to start labelling these things as Alphas.

  2. Brian
    Posted January 30, 2008 at 12:24 pm | Permalink

    That is rubbish comments.

    1.) It is a OS issue triggered by a thirdparty addin. Non MSFT issues, at least not VS ones. Fixed in current OS version.
    2.) Team Explorer does queue a build properly once you connect it to a TFS 2008 Buildserver.
    3.) Overall performance, especially for the build process is way up - up to 70 percent.

    Stop posting crap.

  3. Posted January 30, 2008 at 12:37 pm | Permalink

    Hey Brian,

    1. How is it crap if it’s true. It’s not an OS issue. It’s even listed on the VS2008 feedback pages (https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=311712).

    What’s fixed on current OS version. I’m on windows server 2003 and I haven’t had any related updates recently.

    2. It gives me the option to queue but doesn’t - so my conclusion is that it doesn’t do as it’s supposed to.

    3. Where are you getting your stats. I know it slower, I’m using it.

  4. Posted February 3, 2008 at 2:20 pm | Permalink

    I’m not going to get into the debate of what you and Brian have going on, but I will say this.

    If you are going to post a review, please put more effort into it. Maybe dedicate a paragraph or two for each issue at hand.

    Just a suggestion if you decide to review more products in the future.

    I’m installing it as we speak, and I’m going to attempt to recreate the two issues you speak of and test the performance.

  5. Posted February 3, 2008 at 3:15 pm | Permalink

    After testing out the search functionality using Control + F and Control + Shift + F, there have been absolutely no issues that you described.

    After loading up several CSS files then (50 at the same time), editing them, saving them, and even attempting to overload them… there was no issue at all.

    Finally, after doing some stress testing and a comparison of VS 2005 to VS 2008, there was certainly no performance decrease. Not so in compiling, editing, or any other major functionality.

    This leads me to believe that your computer is infected with viruses/spyware or your computer does not meet the minimum specifications. Also you could consider some conflicting software (like anti-virus).

    So, it is not the application that is the problem, but your computer which has been compromised or not meeting minimum specifications.

    Please revise your review, as it would be the decent thing to do. I’m not a fan of Microsoft, but I am a fan of good journalism; please represent your fellow bloggers in a professional manner.

    Thanks for your time.

  6. Posted February 3, 2008 at 4:49 pm | Permalink

    Hi Guys,

    It seems I have been a little hasty in my review/comments . I’ve re-titled the post accordingly.

    My dev machine is a very fast xeon with 4GB ram and windows sever 2003. Resharper is installed and we use Microsoft Team Foundation Server. I suspect it is a combination of TFS and Resharper that could be causing the speed issues and the crashes.

  7. Paul Barrass
    Posted March 26, 2008 at 2:24 pm | Permalink

    The CSS crashing bug is ReSharper, please help get it fixed by hassling JetBrains and vote for it to be fixed here:

    http://www.jetbrains.net/jira/browse/RSRP-56402

    It’s driving me and my colleague mad!

Post a Comment

Your email is never published nor shared. Required fields are marked *
*
*