A little aside this one; something very, very cool that I’ve noticed with the advent of Visual Studio Update 2 . Without question, this rates as a MUST CHECK OUT Visual Studio feature.
The first complaint (and a valid one, no question about it) in regards to the C# Interactive Window was that running your own code was a little bit of a painstaking process, requiring you to load dlls and supporting references manually, using the #r command. Now, with update 2, initialising C# Interactive with your applications context is a cinch.
For starters, right-click on the project you are interested in and select the Initialize Interactive with Project option, within the Solution Explorer :
Initialise Interactive with Project Option.
This, as you’ll see, does all of the ‘scaffolding’ work for you within the C# Interactive Window, and injects a using statement for the default namespace to get you started. You should see something like the following:
C# Interactive Window Initialised with Project.
From here on in, you are free to start adding using statements, as required, and begin writing code against the types in the target project; in a completely pain-free fashion. A massive thumbs up…you can now go wild, like this for example:
Using Project Code from C# Interactive.
I did try this on a larger, more complex and tightly-coupled code base and I can comfortably say you’ll have issues depending on how things are structured. Smaller, more loosely-coupled types, where SOLID principals have been adhered to are going to allow you to use C# Interactive in this way with more ease.
It is also possible to highlight portions of code, in any file, and right-click the Execute in Interactive option to run with, and execute, smaller chunks of functionality.
Posts on the way to cover some elements of the ASP.NET Web API and Ninject Dependency Injection (hopefully, at some point over the weekend), so watch this space.
Have a good weekend all and I’ll be back with you in a jiffy…