studioshell Releases Rss Feed

Updated Release: StudioShell 1.5 (Apr 25, 2013)

beefarino — Thu, 25 Apr 2013 21:47:42 GMT

1.5 includes many fixes to 1.3.1, as well as new support for VS 2012 and the ISE.

Added Features

You can now add a reference to a project by its name when the project is contained in a solution folder.

*The installer no longer assumes default install locations, and instead uses paths from the registry to locate prerequisites.

43: Add-in and build install support for VS 2012 (Support for VS2012).
Support for PowerShell v3 hosts.
Support for PowerShell v3 tab expansion mechanisms.
Invoke-Item now supported on commandbar buttons (menu items with actions, but not popups). Note that an error is raised if the commandbar button is disabled when invoked; because of this, buttons linked to scriptblocks are not immediately invokable, since these buttons are disabled when the StudioShell runspace is unavailable (such as during a call to invoke-item).
Cache templates are now listed in the dte:/templates hive.
Added Pester unit tests to source hive.

Resolved Issues

Added StudioShellVersion entry to existing psversiontable variable.
Canceling a running pipeline (CTRL+SHIFT+C) doesn't require you to Tonya Harding the entire runspace anymore.
Fixed rename-item implementation to work against multiple matched path nodes.
Fixed CanGet property logic in ShellCodeProperty2.
Removed dependency on PostSharp; this allows StudioShell and PostSharp to be successfully used in the same instance of Visual Studio.
Fixed initialization script errors related to stricter variable interpolation rules introduces in PowerShell v3.
Addressed several issues with command bars; in particular, comboboxes have been removed as a control option since you can't create them via automation anyway.
Buttons are now the default itemtype for new-item when working in the commandbars path node.
The default StudioShell prompt was updated to remove the PowerShell Provider Path preamble in v3 hosts.
42: Massive changes to NuGet init.ps1 logic. NuGet package now verifies the state of your Visual Studio session, as well as checking for installed versions of StudioShell before attempting a module install (Post-install errors).
New-Item in solution/projects no longer appends project file extension to project name. This can cause the VS template mechanism to fail in some situations and seems to set off VS2012 in a big way.
26: Tab expansion behaves closer to the console standard (Studio Shell 1.2 (SSMS) - Tab Completion fails and replace whole line with the parameter).
The StudioShell module no longer adds its internal Scripts folder to the path. This was causing commands to be discovered as both functions of the module and script files, and generally mucking up the help for these script-based commands.
MSI installer now modifies Visual Studio current user registry settings, rather than machine-wide settings.
27: Importing into the ISE is now functional (CodeOwls.StudioShell.Connect not found when importing module in PowerShell ISE).

Released: StudioShell 1.5 (Apr 25, 2013)

Thu, 25 Apr 2013 21:47:41 GMT

1.5 includes many fixes to 1.3.1, as well as new support for VS 2012 and the ISE.

Added Features

You can now add a reference to a project by its name when the project is contained in a solution folder.

*The installer no longer assumes default install locations, and instead uses paths from the registry to locate prerequisites.

43: Add-in and build install support for VS 2012 (Support for VS2012).
Support for PowerShell v3 hosts.
Support for PowerShell v3 tab expansion mechanisms.
Invoke-Item now supported on commandbar buttons (menu items with actions, but not popups). Note that an error is raised if the commandbar button is disabled when invoked; because of this, buttons linked to scriptblocks are not immediately invokable, since these buttons are disabled when the StudioShell runspace is unavailable (such as during a call to invoke-item).
Cache templates are now listed in the dte:/templates hive.
Added Pester unit tests to source hive.

Resolved Issues

Added StudioShellVersion entry to existing psversiontable variable.
Canceling a running pipeline (CTRL+SHIFT+C) doesn't require you to Tonya Harding the entire runspace anymore.
Fixed rename-item implementation to work against multiple matched path nodes.
Fixed CanGet property logic in ShellCodeProperty2.
Removed dependency on PostSharp; this allows StudioShell and PostSharp to be successfully used in the same instance of Visual Studio.
Fixed initialization script errors related to stricter variable interpolation rules introduces in PowerShell v3.
Addressed several issues with command bars; in particular, comboboxes have been removed as a control option since you can't create them via automation anyway.
Buttons are now the default itemtype for new-item when working in the commandbars path node.
The default StudioShell prompt was updated to remove the PowerShell Provider Path preamble in v3 hosts.
42: Massive changes to NuGet init.ps1 logic. NuGet package now verifies the state of your Visual Studio session, as well as checking for installed versions of StudioShell before attempting a module install (Post-install errors).
New-Item in solution/projects no longer appends project file extension to project name. This can cause the VS template mechanism to fail in some situations and seems to set off VS2012 in a big way.
26: Tab expansion behaves closer to the console standard (Studio Shell 1.2 (SSMS) - Tab Completion fails and replace whole line with the parameter).
The StudioShell module no longer adds its internal Scripts folder to the path. This was causing commands to be discovered as both functions of the module and script files, and generally mucking up the help for these script-based commands.
MSI installer now modifies Visual Studio current user registry settings, rather than machine-wide settings.
27: Importing into the ISE is now functional (CodeOwls.StudioShell.Connect not found when importing module in PowerShell ISE).

Updated Release: StudioShell 1.5 (Feb 15, 2013)

beefarino — Fri, 15 Feb 2013 14:09:42 GMT

1.5 includes many fixes to 1.3.1, as well as new support for VS 2012 and the ISE.

Added Features

43: Add-in and build install support for VS 2012 (Support for VS2012).
Support for PowerShell v3 hosts.
Support for PowerShell v3 tab expansion mechanisms.
Invoke-Item now supported on commandbar buttons (menu items with actions, but not popups). Note that an error is raised if the commandbar button is disabled when invoked; because of this, buttons linked to scriptblocks are not immediately invokable, since these buttons are disabled when the StudioShell runspace is unavailable (such as during a call to invoke-item).
Cache templates are now listed in the dte:/templates hive.
Added Pester unit tests to source hive.

Resolved Issues

Canceling a running pipeline (CTRL+SHIFT+C) doesn't require you to Tonya Harding the entire runspace anymore.
Fixed rename-item implementation to work against multiple matched path nodes.
Fixed CanGet property logic in ShellCodeProperty2.
Removed dependency on PostSharp; this allows StudioShell and PostSharp to be successfully used in the same instance of Visual Studio.
Fixed initialization script errors related to stricter variable interpolation rules introduces in PowerShell v3.
Addressed several issues with command bars; in particular, comboboxes have been removed as a control option since you can't create them via automation anyway.
Buttons are now the default itemtype for new-item when working in the commandbars path node.
The default StudioShell prompt was updated to remove the PowerShell Provider Path preamble in v3 hosts.
42: Massive changes to NuGet init.ps1 logic. NuGet package now verifies the state of your Visual Studio session, as well as checking for installed versions of StudioShell before attempting a module install (Post-install errors).
New-Item in solution/projects no longer appends project file extension to project name. This can cause the VS template mechanism to fail in some situations and seems to set off VS2012 in a big way.
26: Tab expansion behaves closer to the console standard (Studio Shell 1.2 (SSMS) - Tab Completion fails and replace whole line with the parameter).
The StudioShell module no longer adds its internal Scripts folder to the path. This was causing commands to be discovered as both functions of the module and script files, and generally mucking up the help for these script-based commands.
MSI installer now modifies Visual Studio current user registry settings, rather than machine-wide settings.
27: Importing into the ISE is now functional (CodeOwls.StudioShell.Connect not found when importing module in PowerShell ISE).

Released: StudioShell 1.5 (Feb 15, 2013)

Fri, 15 Feb 2013 14:09:42 GMT

1.5 includes many fixes to 1.3.1, as well as new support for VS 2012 and the ISE.

Added Features

43: Add-in and build install support for VS 2012 (Support for VS2012).
Support for PowerShell v3 hosts.
Support for PowerShell v3 tab expansion mechanisms.
Invoke-Item now supported on commandbar buttons (menu items with actions, but not popups). Note that an error is raised if the commandbar button is disabled when invoked; because of this, buttons linked to scriptblocks are not immediately invokable, since these buttons are disabled when the StudioShell runspace is unavailable (such as during a call to invoke-item).
Cache templates are now listed in the dte:/templates hive.
Added Pester unit tests to source hive.

Resolved Issues

Canceling a running pipeline (CTRL+SHIFT+C) doesn't require you to Tonya Harding the entire runspace anymore.
Fixed rename-item implementation to work against multiple matched path nodes.
Fixed CanGet property logic in ShellCodeProperty2.
Removed dependency on PostSharp; this allows StudioShell and PostSharp to be successfully used in the same instance of Visual Studio.
Fixed initialization script errors related to stricter variable interpolation rules introduces in PowerShell v3.
Addressed several issues with command bars; in particular, comboboxes have been removed as a control option since you can't create them via automation anyway.
Buttons are now the default itemtype for new-item when working in the commandbars path node.
The default StudioShell prompt was updated to remove the PowerShell Provider Path preamble in v3 hosts.
42: Massive changes to NuGet init.ps1 logic. NuGet package now verifies the state of your Visual Studio session, as well as checking for installed versions of StudioShell before attempting a module install (Post-install errors).
New-Item in solution/projects no longer appends project file extension to project name. This can cause the VS template mechanism to fail in some situations and seems to set off VS2012 in a big way.
26: Tab expansion behaves closer to the console standard (Studio Shell 1.2 (SSMS) - Tab Completion fails and replace whole line with the parameter).
The StudioShell module no longer adds its internal Scripts folder to the path. This was causing commands to be discovered as both functions of the module and script files, and generally mucking up the help for these script-based commands.
MSI installer now modifies Visual Studio current user registry settings, rather than machine-wide settings.
27: Importing into the ISE is now functional (CodeOwls.StudioShell.Connect not found when importing module in PowerShell ISE).

Created Release: StudioShell 1.5 (Feb 03, 2013)

beefarino — Mon, 04 Feb 2013 00:29:28 GMT

1.5 includes many fixes to 1.3.1, as well as new support for VS 2012 and the ISE.

Added Features

43: Add-in and build install support for VS 2012 (Support for VS2012).
Support for PowerShell v3 hosts.
Support for PowerShell v3 tab expansion mechanisms.
Invoke-Item now supported on commandbar buttons (menu items with actions, but not popups). Note that an error is raised if the commandbar button is disabled when invoked; because of this, buttons linked to scriptblocks are not immediately invokable, since these buttons are disabled when the StudioShell runspace is unavailable (such as during a call to invoke-item).
Cache templates are now listed in the dte:/templates hive.
Added Pester unit tests to source hive.

Resolved Issues

Canceling a running pipeline (CTRL+SHIFT+C) doesn't require you to Tonya Harding the entire runspace anymore.
Fixed rename-item implementation to work against multiple matched path nodes.
Fixed CanGet property logic in ShellCodeProperty2.
Removed dependency on PostSharp; this allows StudioShell and PostSharp to be successfully used in the same instance of Visual Studio.
Fixed initialization script errors related to stricter variable interpolation rules introduces in PowerShell v3.
Addressed several issues with command bars; in particular, comboboxes have been removed as a control option since you can't create them via automation anyway.
Buttons are now the default itemtype for new-item when working in the commandbars path node.
The default StudioShell prompt was updated to remove the PowerShell Provider Path preamble in v3 hosts.
42: Massive changes to NuGet init.ps1 logic. NuGet package now verifies the state of your Visual Studio session, as well as checking for installed versions of StudioShell before attempting a module install (Post-install errors).
New-Item in solution/projects no longer appends project file extension to project name. This can cause the VS template mechanism to fail in some situations and seems to set off VS2012 in a big way.
26: Tab expansion behaves closer to the console standard (Studio Shell 1.2 (SSMS) - Tab Completion fails and replace whole line with the parameter).
The StudioShell module no longer adds its internal Scripts folder to the path. This was causing commands to be discovered as both functions of the module and script files, and generally mucking up the help for these script-based commands.
MSI installer now modifies Visual Studio current user registry settings, rather than machine-wide settings.
27: Importing into the ISE is now functional (CodeOwls.StudioShell.Connect not found when importing module in PowerShell ISE).

Released: StudioShell 1.5 (Feb 03, 2013)

Mon, 04 Feb 2013 00:29:28 GMT

1.5 includes many fixes to 1.3.1, as well as new support for VS 2012 and the ISE.

Added Features

43: Add-in and build install support for VS 2012 (Support for VS2012).
Support for PowerShell v3 hosts.
Support for PowerShell v3 tab expansion mechanisms.
Invoke-Item now supported on commandbar buttons (menu items with actions, but not popups). Note that an error is raised if the commandbar button is disabled when invoked; because of this, buttons linked to scriptblocks are not immediately invokable, since these buttons are disabled when the StudioShell runspace is unavailable (such as during a call to invoke-item).
Cache templates are now listed in the dte:/templates hive.
Added Pester unit tests to source hive.

Resolved Issues

Canceling a running pipeline (CTRL+SHIFT+C) doesn't require you to Tonya Harding the entire runspace anymore.
Fixed rename-item implementation to work against multiple matched path nodes.
Fixed CanGet property logic in ShellCodeProperty2.
Removed dependency on PostSharp; this allows StudioShell and PostSharp to be successfully used in the same instance of Visual Studio.
Fixed initialization script errors related to stricter variable interpolation rules introduces in PowerShell v3.
Addressed several issues with command bars; in particular, comboboxes have been removed as a control option since you can't create them via automation anyway.
Buttons are now the default itemtype for new-item when working in the commandbars path node.
The default StudioShell prompt was updated to remove the PowerShell Provider Path preamble in v3 hosts.
42: Massive changes to NuGet init.ps1 logic. NuGet package now verifies the state of your Visual Studio session, as well as checking for installed versions of StudioShell before attempting a module install (Post-install errors).
New-Item in solution/projects no longer appends project file extension to project name. This can cause the VS template mechanism to fail in some situations and seems to set off VS2012 in a big way.
26: Tab expansion behaves closer to the console standard (Studio Shell 1.2 (SSMS) - Tab Completion fails and replace whole line with the parameter).
The StudioShell module no longer adds its internal Scripts folder to the path. This was causing commands to be discovered as both functions of the module and script files, and generally mucking up the help for these script-based commands.
MSI installer now modifies Visual Studio current user registry settings, rather than machine-wide settings.
27: Importing into the ISE is now functional (CodeOwls.StudioShell.Connect not found when importing module in PowerShell ISE).

Updated Release: StudioShell 1.3.1 (Jul 03, 2012)

beefarino — Tue, 03 Jul 2012 19:01:55 GMT

1.3 is a maintenance release that addresses several bugs and feature shortcomings.

1.3.1

The initial release of 1.3 contained a bug that broke the path topology management mechanism, effectively leaving the following path nodes useless: /solution/codemodel; /selectedItems/codemodel.

1.3.0

Project folders now support the new-item cmdlet properly.
The exit command closes the console window but not reset the PowerShell session. A new menu command was added to reset the session. This command effectively associates a new PowerShell runspace with the StudioShell console. The reason the exit command doesn't reset the console session is that there are many features of StudioShell that rely on the underlying PowerShell runspace backing the console. E.g., solution modules.

The StudioShell console now supports multi-line statements and nested prompting. E.g., if you enter a command and a pipe, the console will prompt you for the next pipeline command.

The NuGet initialization script would fail if the AddIns folder did not exist. Now the AddIn folder is explicitly created.

It was not possible to specify a path to an assembly file when adding a reference to the dte:/solution/projects/.../references node. PowerShell would interpret the file path as part of the item path. The reference collection node was modified to accept an assembly path or name in the new-item -value parameter.

Released: StudioShell 1.3.1 (Jul 03, 2012)

Tue, 03 Jul 2012 19:01:55 GMT

1.3 is a maintenance release that addresses several bugs and feature shortcomings.

1.3.1

The initial release of 1.3 contained a bug that broke the path topology management mechanism, effectively leaving the following path nodes useless: /solution/codemodel; /selectedItems/codemodel.

1.3.0

Project folders now support the new-item cmdlet properly.
The exit command closes the console window but not reset the PowerShell session. A new menu command was added to reset the session. This command effectively associates a new PowerShell runspace with the StudioShell console. The reason the exit command doesn't reset the console session is that there are many features of StudioShell that rely on the underlying PowerShell runspace backing the console. E.g., solution modules.

The StudioShell console now supports multi-line statements and nested prompting. E.g., if you enter a command and a pipe, the console will prompt you for the next pipeline command.

The NuGet initialization script would fail if the AddIns folder did not exist. Now the AddIn folder is explicitly created.

It was not possible to specify a path to an assembly file when adding a reference to the dte:/solution/projects/.../references node. PowerShell would interpret the file path as part of the item path. The reference collection node was modified to accept an assembly path or name in the new-item -value parameter.

Updated Release: StudioShell 1.3 (Jun 22, 2012)

beefarino — Mon, 25 Jun 2012 18:42:18 GMT

1.3 is a maintenance release that addresses several bugs and feature shortcomings.

Project folders now support the new-item cmdlet properly.
The exit command closes the console window but not reset the PowerShell session. A new menu command was added to reset the session. This command effectively associates a new PowerShell runspace with the StudioShell console. The reason the exit command doesn't reset the console session is that there are many features of StudioShell that rely on the underlying PowerShell runspace backing the console. E.g., solution modules.

The StudioShell console now supports multi-line statements and nested prompting. E.g., if you enter a command and a pipe, the console will prompt you for the next pipeline command.

The NuGet initialization script would fail if the AddIns folder did not exist. Now the AddIn folder is explicitly created.

It was not possible to specify a path to an assembly file when adding a reference to the dte:/solution/projects/.../references node. PowerShell would interpret the file path as part of the item path. The reference collection node was modified to accept an assembly path or name in the new-item -value parameter.

Released: StudioShell 1.3 (Jun 22, 2012)

Mon, 25 Jun 2012 18:42:18 GMT

1.3 is a maintenance release that addresses several bugs and feature shortcomings.

Project folders now support the new-item cmdlet properly.
The exit command closes the console window but not reset the PowerShell session. A new menu command was added to reset the session. This command effectively associates a new PowerShell runspace with the StudioShell console. The reason the exit command doesn't reset the console session is that there are many features of StudioShell that rely on the underlying PowerShell runspace backing the console. E.g., solution modules.

The StudioShell console now supports multi-line statements and nested prompting. E.g., if you enter a command and a pipe, the console will prompt you for the next pipeline command.

The NuGet initialization script would fail if the AddIns folder did not exist. Now the AddIn folder is explicitly created.

It was not possible to specify a path to an assembly file when adding a reference to the dte:/solution/projects/.../references node. PowerShell would interpret the file path as part of the item path. The reference collection node was modified to accept an assembly path or name in the new-item -value parameter.

Created Release: StudioShell 1.3 (Jun 22, 2012)

beefarino — Fri, 22 Jun 2012 20:02:07 GMT

1.3 is a maintenance release that addresses several bugs and feature shortcomings.

Project folders now support the new-item cmdlet properly.
The exit command closes the console window but not reset the PowerShell session. A new menu command was added to reset the session. This command effectively associates a new PowerShell runspace with the StudioShell console. The reason the exit command doesn't reset the console session is that there are many features of StudioShell that rely on the underlying PowerShell runspace backing the console. E.g., solution modules.

The StudioShell console now supports multi-line statements and nested prompting. E.g., if you enter a command and a pipe, the console will prompt you for the next pipeline command.

The NuGet initialization script would fail if the AddIns folder did not exist. Now the AddIn folder is explicitly created.

It was not possible to specify a path to an assembly file when adding a reference to the dte:/solution/projects/.../references node. PowerShell would interpret the file path as part of the item path. The reference collection node was modified to accept an assembly path or name in the new-item -value parameter.

Released: StudioShell 1.3 (Jun 22, 2012)

Fri, 22 Jun 2012 20:02:07 GMT

1.3 is a maintenance release that addresses several bugs and feature shortcomings.

Project folders now support the new-item cmdlet properly.
The exit command closes the console window but not reset the PowerShell session. A new menu command was added to reset the session. This command effectively associates a new PowerShell runspace with the StudioShell console. The reason the exit command doesn't reset the console session is that there are many features of StudioShell that rely on the underlying PowerShell runspace backing the console. E.g., solution modules.

The StudioShell console now supports multi-line statements and nested prompting. E.g., if you enter a command and a pipe, the console will prompt you for the next pipeline command.

The NuGet initialization script would fail if the AddIns folder did not exist. Now the AddIn folder is explicitly created.

It was not possible to specify a path to an assembly file when adding a reference to the dte:/solution/projects/.../references node. PowerShell would interpret the file path as part of the item path. The reference collection node was modified to accept an assembly path or name in the new-item -value parameter.

Created Release: StudioShell 1.2.1

beefarino — Fri, 06 Jan 2012 21:25:55 GMT

Wrap up of issues resolved from 1.2

Updated Release: StudioShell 1.2 (Dec 28, 2011)

beefarino — Fri, 30 Dec 2011 05:03:08 GMT

Upgrading

The installer will upgrade your previous StudioShell installations. There is no need to uninstall them before running this installer.

Change Log

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.

Released: StudioShell 1.2 (Dec 28, 2011)

Fri, 30 Dec 2011 05:03:08 GMT

Upgrading

The installer will upgrade your previous StudioShell installations. There is no need to uninstall them before running this installer.

Change Log

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

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)

Refactored Path Topology

Extensive Internal Refactoring

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.

Updated Release: StudioShell 1.2 (Dec 28, 2011)

beefarino — Fri, 30 Dec 2011 05:02:31 GMT

Upgrading

The installer will upgrade your previous StudioShell installations. There is no need to uninstall them before running this installer.

Change Log

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

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)

Refactored Path Topology

Extensive Internal Refactoring

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.

Updated Release: StudioShell 1.0.1 (Mar 11, 2011)

beefarino — Fri, 11 Mar 2011 22:03:56 GMT

Upgrading

The 1.0.1 installer will upgrade your 1.0 installation, there is no need to remove it before running the new installer.

Change Log

This release contains several fixes from the initial 1.0 release. Most of these are hardening for Visual Studio 2010.

Resolved Issues

Tab Completion can cause crash in VS2010: Tab completion and history walking have been hardened in the console.

Can not CD into project with dots in its name,Cannot CD into projects inside of solution directories: Solution Folders are now recognized as containers in the console.

Solution Modules not unloaded automatically: Solution Modules are now unloaded automatically if the
"AutoManageSolutionProfiles" setting is enabled.

studioshell should use private profile: The PowerShell AllUsersCurrentHost is no longer loaded. The
"LoadPowerShellProfiles" setting now only applies
to your Current User profile script located at
~\documents\windowspowershell\profile.ps1.

Visualization Data Panes don't reliably appear in VS 2010: Data panes (visualizations) now reliably appear in VS2010.

Console window not filling parent window client area on startup in VS2010: The default console window now consumes all available client area of
the tool window at startup.

Added Features

Project item properties not available as paths: Project item properties are now avaialble in the path heirarchy.
See dte:/solution/projects/<project>/<file>/properties.

The locals and arguments nodes under the stack frame tree now add missing
quotes to strings when you attempt to set an expression value.

The default PowerShell module path is now added to the process environment
when StudioShell is started.

Added about_StudioShell_Version help topic with changelog

Released: StudioShell 1.0.1 (Mar 11, 2011)

Fri, 11 Mar 2011 22:03:56 GMT

Upgrading

The 1.0.1 installer will upgrade your 1.0 installation, there is no need to remove it before running the new installer.

Change Log

This release contains several fixes from the initial 1.0 release. Most of these are hardening for Visual Studio 2010.

Resolved Issues

Added Features

Created Release: StudioShell 1.0.1 (Mar 11, 2011)

beefarino — Fri, 11 Mar 2011 22:02:53 GMT

Upgrading

The 1.0.1 installer will upgrade your 1.0 installation, there is no need to remove it before running the new installer.

Change Log

This release contains several fixes from the initial 1.0 release. Most of these are hardening for Visual Studio 2010.

Resolved Issues

Added Features

Updated Release: StudioShell 1.0 (Feb 28, 2011)

beefarino — Tue, 01 Mar 2011 00:57:11 GMT

This is the initial public release of StudioShell.

There are plenty of wrinkles to iron out, so please report any issues using the Issues Tracker.

Notes:

Some people are reporting crashes when using tab completion in the default console in Visual Studio 2010.
There are ample warnings in the online documentation and console, but if you chose to use the "Old School" process I/O console, do be careful that you don't type the exit command or close the console window, as this will end the Visual Studio process without saving any unsaved work.