Home » Headline | Tools

VS2010 with a real project

4. May 2010 by thebeebs 0 Comments

vs2010 I’ve had access to VS2010 for the past 4 months but the last 2 weeks was the first time I'd used it to produce production code (yeah I really produce that little code these days), I was helping some customers produce IE8 Webslices and Accelerators.

I thought I'd provide a quick round up of some of the features that really got me loving VS2010.


Test Impact

I like to claim I always do TDD but in reality, as a product matures, I often will often refactor a line or method without writing the test to first mandate it. In VS2010 as you make changes to your code the Test Explorer tells you how many tests are impacted by the code change. This is a useful indicator of how big a change you are making and enables you to run a subset of the tests rather than all the tests... this helped speed up the refactor test cycle as I didn’t need to run through 900 tests when I knew with some certainty that my change only impacted 10 of them.



The profiling in VS2010 not only allows you to find bottlenecks in your standard C# but also lets you interrogate the Asynchronous calls that JQuery makes. This helped me discover a bug where I had a JQuery Timer making a heavy Database call, It worked fine with a single instance but when I scaled it up to a larger load my CPU utilization went through the roof.


Automated UI testing

A lot of the webslices I produced had complex UI so having User Interface Testing built into VS2010 ensured that modifications I made didn’t effect the user experience. Good UI regression testing catches many common avoidable mistakes.


Anonymisation of Data

Before VS2010 I’d have used RedGate tools to generate anonymous test data, now I can do it easily from within Visual studio. Which is helpful, when in our instance, we knew the schema we were working to but because of data protection we couldn’t have access to the actual data.


TDD improvements

Its now easier for VS2010 to stub methods which enables quicker red/green/refactor cycles. Also I liked that I could create a new class and specify the Namespace and Project that I wanted it created in rather than the class being created in the Test Project and then having to manually more it.


Azure Publishing

Publishing to azure is getting so simple it’s scary, with an MSDN subscription you get 750 hours free. In VS2010 you just need to right click the webrole and choose publish then upload the two files it creates to Azure. Cloud computing doesn't get much easier.


I haven’t even touched on intelitrace and all the other crazy goodness in the new release but when I do I'll be sure to update you.

Add comment

(Will show your Gravatar icon)  

  Country flag

  • Comment
  • Preview