Visual Studio Myths – busted wide open

The team and I were having a conversation about developers (we do that from time to time). It went something like:

  • “Isn’t it a shame that so many developers are stuck on Visual Studio 2005 when Visual Studio 2008 would be way better for them and Visual Studio 2010 is just around the corner”
  • “Why is that?”
  • “And… then there are all these myths that developers believe to be true which hold them back from adopting Visual Studio 2008. For instance many developers believe that …”
  • “OK. What can we do to help them?”

Well, after several iterations of ideas on how we could do our little bit to address this, we decided to go with collating:

  • All the key feature improvements from Visual Studio 2005 through to Visual Studio 2010 by focus area (web, data etc)
  • All the myths we heard in our meetings and events, plus some we made up to pad it out 🙂

And then, with a little help from an agency, we created a Silverlight 3 application which presented the information in a way that developers will hopefully find rather useful and a little prettier than the whopping bit word document we created.

The final result is the Visual Studio Myth Busting Matrix.


This is a release candidate – both of the application and the content. The Visual Studio 2010 content is based on Beta 1 and will definitely be updated for Beta 2. We are really, really keen to get your feedback. We would love to know:

  • If you had any problems using it.
  • If you found it useful.
  • Any myths it busted for you.
  • Any answers to myths you disagree with.
  • Whether you think it is useful format vs more traditional approaches (For instance, we could do a version for your managers to help them see why you would be more productive using the latest tools)

And most importantly any features or myths you think we missed.

Feel free to contact me through my blog, through twitter or just tweet with the tag #dotnetmyth which we will be watching.


P.S. And it does have spinning balls. Which I know MikeT (See rant!) and MikeO particularly admire 🙂

Using the Myth Buster

Hopefully all is reasonably obvious.

Select a version of Visual Studio (2005/2008/2010)


Choose your focus (Rich Client, Web, Data, IDE etc)


Expand Features


Click on “read more” to… read some more


Expand Myths



Optionally, tweet the myth out if you think it worthy (we are using #dotnetmyth as the tag)


Comments (1)

  1. Steve Hiner says:

    Thought I'd share one reason why I'm still using VS05.  We work with WinCE and as far as I can tell the WinCE 6 platform builder tools only work in VS05, not VS08.  I wish I could use VS08 with the tools.

    Thought I'd also share the reason why I haven't done any WPF projects despite the fact that I'd really like to.  About 90% of all the WPF apps I've seen have been painfully underperforming on my hardware.  My perception is that WPF is slow slow slow.  That's contrary to what I expected since GDI isn't really hardware accellerated and I thought WPF was going to run through the DirectX engine.  I've only seen a couple WPF apps that didn't feel sluggish.  It needs to perform well on real-world hardware – I can't expect my users to be running newer dual core procs with super high end video cards.  I realize that the apps I've seen might have been poorly coded but some of them were released as WPF samples by MS so I assume they are doing things the "right way" in WPF.

    That's my 2 cents.

Skip to main content