Top Ten Reasons to Not Buy Visual Studio 2008

For those of you who can’t view video because you are at work (and are probably still using Visual Studio 2002 or 2003) I’ve included the relevant text below.

10. Visual Studio Already Does Everything.

9. You believe that WPF, ajax, and Silverlight are dumb fads.

8. Real programmers don’t use SQL so you won’t be using LINQ.

7. anonymous types make the code unreadable.

6. You forgot to renew your MSDN subscription and you are having a root canal done on the day of the InstallFest

5. You don’t have time to upgrade (but you have time to write more code)

4. You get paid by the lines of code you write.

3. You only have a computer with a single core CPU and 256 Meg or memory.

2. You are still waiting for Borland to make a comeback.

And the number one reason why you shouldn’t upgrade to Visual Studio 2008?!

1. You are still using NotePad and the command line compiler to do all your development.

Technorati Tags:

 del.icio.us Tags:

Related Post

8 Responses to “Top Ten Reasons to Not Buy Visual Studio 2008”

  • [...] the Top Ten Reasons to Not Buy Visual Studio 2008 Posted: Dec 01 2007, 11:30 AM by c1sbc Filed under: .NET Framework, Community News, General [...]

  • There is a bit of truth to #10, Visual Studio 2005 already does everything. I’m working on an ASP.NET 3.5 web site using Visual Studio 2005 until I get Visual Studio 2008. It does not cause any problems because I’m not using anything that isn’t in ASP.NET 2.0, even though my web.config file is for ASP.NET 3.5.

  • Dave:

    Robert, you need to look at the rest of my post for the last week. Yes, you COULD compile with 2.0 against the 3.5 libraries. But, there are some pretty significant language changes in both VB and C# as well as some pretty nice IDE changes, that you just won’t be able to use until or unless you move to 2008.

  • #1 is not funny! During the beta of 1.0 I actually did that! OMG. :)

  • jc:

    You forgot… “Your Company still requires you to use .NET 1.1″

  • Stephane:

    And… because .NET 3.5 it’s not programming. It’s mapping.
    And LINQ it’s for developer who don’t know stored proc. LINQ it’s for ACCESS/FoxPro developer.

  • AaronZ:

    I just got back from InstallFest with my copy of VS 2008 Pro, yours was the last blog I read before signing off for the night (the Patriots just beat the Ravens). Thank you for a good laugh!

    BTW, papyrus and my trusty abacus still work just fine. I mock your fancy magic powered ‘corn-puters’!

  • I love you so much! Great place to visit!,