# Sunday, November 23, 2008
« .NET console applications are so old sch... | Main | Thinking of Mobile Development »
Wasting 2 Hours

I was going to do some quick coding this morning on a project.  Haha...  2 hours later I still haven't started to write any code.  Why?  Visual Studio 2008 updates which I needed to be able to open the solution and be productive.

  1. Installed the TFS client, which took a while.
  2. Installed VS 2008 SP1.
  3. I had to reinstall VS 2008 checking the "Unit Testing Tools" checkbox (see image).
  4. Upgraded ReSharper 4.0 to 4.1
  5. Installed the VS 2008 SP1 hotfix (KB958502) to add JScript intellisense support from "-vsdoc.js" files.

Number 3 was a bit strange.  I opened the solution only to find VS complaining about an unsupported project type.  I guess when I initially installed VS 2008 I figured I would never be using MSTest.  If only that were still true.

image

I installed KB958502 to get intellisense specifically for JQuery, since there is now a -vsdoc.js file available on the JQuery site.

You know, it seems like VS 2008 isn't all that far behind VS 2005 in regards to the number of installation steps/packages required to get a usable environment (at least for this project).

Visual Studio
Sunday, November 23, 2008 7:58:20 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [2]  |  Related posts:
ReSharper 5 won't run unit tests in Visual Studio 2010
Visual Studio webtests hurt my eyes
Check for parameter null, more ReSharper goodness
ReSharper 4.5 MsTest Plugin
Running Simian from Visual Studio with clickable links
MSTest ReSharper 4 Plugin
Tuesday, November 25, 2008 9:00:20 AM (GMT Standard Time, UTC+00:00)
Updating your dev tools is always such a hassle. Visual Studio and all of its assorted add-ins are the worst in that regard. That is why I myself sometimes take a while to upgrade any dev tools (even the simple ones) because of the time commit.

I'm curious, does VS 2008 SP1 take just as long to install as the SP1 for VS 2005? That was a huge time killer.

Usually, smart, lazy programmers use a lot of different tools to get the job done but the price is not only learning them but maintaining them as well. It is very likely this is the reason why the average .NET developer probably only uses VS out of the box and nothing else if they can avoid it. Installing VS alone is plenty of work as it is so why bother with anything else.

Too bad that an easy-to-use, low or no cost uber-tool doesn't already exist to manage all this for you. (hint hint)
Ray Vega
Thursday, December 11, 2008 5:04:21 AM (GMT Standard Time, UTC+00:00)
Additionally I had to overcome a bug in Visual SVN. I was getting an error for the MSTest projects, "The project 'Xxxxxxxx' is under source control. This version of Visual Studio.Net
does not support source controlled projects. Apparently there's a bug in the version of VisualSVN that I was using that caused this. It took me almost an hour to figure that out.
Sneal
Comments are closed.