This project is read-only.

Why nuget and not an extension

Feb 15, 2012 at 3:49 PM

Why is this shipped as a nuget package and not an extension?  This seems odd to me.

Feb 15, 2012 at 5:17 PM

The only reason StudioShell is shipped as a nuget package is to better enable its use inside of other nuget packages.  StudioShell makes it simple to extend the IDE command structure, which makes it a good choice to use in your own nuget packages.  In order to support this usage scenario (where a nuget package depends on StudioShell, which the user may or may not have installed), StudioShell has to be available in the nuget package repository.

StudioShell is not a "full" VS extension, but rather an add-in.  This allows it to support VS 2008 and 2010, but excludes it from the extension manager of VS 2010.