Automating Visual Studio with StudioShell and Nuget


StudioShell’s goal is to fundamentally change the way you interact with Visual Studio and your code.

If you’ve ever implemented a Visual Studio extension, such as an add-in or a package, you know how convoluted this space has become. You have to become an expert in your tooling if you want to change it. StudioShell changes this landscape by exposing many of Visual Studio’s extensibility points in a simple and consistent way. It makes the Visual Studio SDK interactive and discoverable. What an extension does in a compiled binary, StudioShell can accomplish with a one-liner.

The latest release of StudioShell is designed to work specifically inside of the Package Manager console and your Nuget packages. This means that your Nuget packages can now easily manipulate any aspect of the Visual Studio SDK as part of their installation. This offers some tantalizing possibilities, such as custom context menu items tied to bits of script.

During this session I will demonstrate how easy it is to make Visual Studio and Nuget not just a tool you use, but *your* tool. Demos will include a conditional refactoring that cannot be accomplished using any existing Visual Studio extensions, as well as way to customize the IDE and UI from a Nuget package.

You will leave this session with your mind blown and full of amazing ideas. I guarantee, the first thing you’ll do when you get home from Philly Code Camp is install StudioShell.

Jim Christopher

Jim Christopher is an independent software consultant with 19 years of professional experience spanning highly-regulated industries such as defense, education, and casino gaming systems. He currently runs Code Owls LLC, a Charlotte NC company focused on automation and integration projects. Jim is a Pluralsight author, three-time PowerShell MVP, Blue Diamond Technology award winner, and manages about a dozen open source projects. In his off time he plays guitar, ukulele, and participates in various acts of nogoodnicking.