The installer will upgrade your previous StudioShell installations. There is no need to uninstall them before running this installer.
StudioShell 1.2 is a wrap-up of several private refactoring builds, extensions, and bug fixes. Of particular note in this release:
Support for NuGet
All StudioShell features can be used in the NuGet package manager console. Previously the bulk of the feature set was available, but custom UI commands would not work.
In addition, as of this release StudioShell can be installed into Visual Studio 2010 as a NuGet package from the default public repository.
For more information, see aboutStudioShellNuGet.
Support for the Standard PowerShell Console.
StudioShell can now be used from the standard PowerShell console. The DTE: drive and most extensibility features are supported.
For more information, see aboutStudioShellPowerShell.
Support for SQL Server Management Studio 2012 (Denali)
StudioShell can now be integrated with SQL Server Management Studio Denali. This feature should be considered experimental for the time being; if you are interested in picking up this ball and running with it please let me know.
For more information, see aboutStudioShellSSMS.
Refactored Path Topology
After a lot of feedback I decided that the layout of the DTE: drive was not optimal for some core usage scenarios. For example, the project model and code model were housed under the same path tree, making recursive operations on either code or project items far slower than necessary.
Significant effort was aimed at refactoring the DTE: drive topology to support more efficient use. Knowing that many people have scripts that rely on the 1.0 path layout, a mechanism for maintaining backwards compatibility was also introduced.
For more information on the path topology changes in this release, see aboutStudioShellVersion.
For more information on maintaining backward compatibility with your 1.0 scripts, see the use-pathTopologyVersion cmdlet.
Extensive Internal Refactoring
The previous releases of StudioShell consisted of a monolithic assembly and small PowerShell module. After learning much about providers and hosting, the internal code base of StudioShell is a lot better organized.
And of course ... Plenty of Fixes
Many thanks to those who have submitted issues and helped work the problems with this project. Keep those bug reports coming in.