studioshell Wiki Rss Feed

Updated Wiki: Home

beefarino — Thu, 06 Jun 2013 23:39:30 GMT

Overview

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 IDE interactive and discoverable.

What an add-in does in a compiled binary, StudioShell can accomplish with a one-liner.

Current Release

The current release of StudioShell is 1.5.1. For more information, see StudioShell 1.5.1. This release has been classified as "stable" and is recommended for use over previous releases.

StudioShell is also available as a NuGet package for Visual Studio 2010 and 2012. StudioShell can also be installed with Chocolatey.

Getting Involved

There are several ways you can get involved in this project:

Contribute your scripts to the StudioShell.Contrib project.
Use StudioShell and log any issues using the Issue Tracker.
If you are interested in expanding support for the SSMS object model in StudioShell, please contact the project coordinator.
If you are interested in expanding the DTE provider with additional features of the Visual Studio service offering, please contact the project coordinator.

Features

The features supported by StudioShell include:

Support for standard PowerShell profile scripts, as well as StudioShell profile scripts - customize your StudioShell session as you would any other PowerShell session.
Manage your projects, references, breakpoints, stack frame locals, menus, toolbars, Visual Studio settings, IDE windows, and even your code from PowerShell scripts, all in a consistent and discoverable way.
Solution Modules - save your StudioShell and IDE customizations as a PowerShell module in your solution, and it will automatically be imported into your StudioShell session when the solution is loaded.
Simple visualization controls you can invoke from the console - create a graph of project code statistics with one line of script.
Fully integrated context-sensitive help.
Host indifference - StudioShell features can be used from any suitable PowerShell host, including NuGet, the standard PowerShell console, and the Integrated Scripting Environment.

For more specific features and examples, please see Examples and Documentation

Demos

A deeply integrated Mercurial file status monitor with two lines of PowerShell:

Launch in another window

Exploring the DTE provider:

Launch in another window

Updated Wiki: Home

beefarino — Tue, 28 May 2013 15:27:11 GMT

Overview

Current Release

Getting Involved

There are several ways you can get involved in this project:

Contribute your scripts to the StudioShell.Contrib project.
Use StudioShell and log any issues using the Issue Tracker.
If you are interested in expanding support for the SSMS object model in StudioShell, please contact the project coordinator.
If you are interested in expanding the DTE provider with additional features of the Visual Studio service offering, please contact the project coordinator.

Features

The features supported by StudioShell include:

Support for standard PowerShell profile scripts, as well as StudioShell profile scripts - customize your StudioShell session as you would any other PowerShell session.
Manage your projects, references, breakpoints, stack frame locals, menus, toolbars, Visual Studio settings, IDE windows, and even your code from PowerShell scripts, all in a consistent and discoverable way.
Solution Modules - save your StudioShell and IDE customizations as a PowerShell module in your solution, and it will automatically be imported into your StudioShell session when the solution is loaded.
Simple visualization controls you can invoke from the console - create a graph of project code statistics with one line of script.
Fully integrated context-sensitive help.
Host indifference - StudioShell features can be used from any suitable PowerShell host, including NuGet, the standard PowerShell console, and the Integrated Scripting Environment.

For more specific features and examples, please see Examples and Documentation

Demos

A deeply integrated Mercurial file status monitor with two lines of PowerShell:

Launch in another window

Exploring the DTE provider:

Launch in another window

Updated Wiki: Home

beefarino — Sat, 25 May 2013 19:20:10 GMT

Overview

Current Release

The current release of StudioShell is 1.5. For more information, see StudioShell 1.5. Although this release is still classified as "beta", it is recommended for use over 1.2 and 1.31 as it fixes many issues with the previous releases.

The StudioShell beta is also available as a NuGet package for Visual Studio 2010 and 2012.

Getting Involved

There are several ways you can get involved in this project:

Contribute your scripts to the StudioShell.Contrib project.
Use StudioShell and log any issues using the Issue Tracker.
If you are interested in expanding support for the SSMS object model in StudioShell, please contact the project coordinator.
If you are interested in expanding the DTE provider with additional features of the Visual Studio service offering, please contact the project coordinator.

Features

The features supported by StudioShell include:

Support for standard PowerShell profile scripts, as well as StudioShell profile scripts - customize your StudioShell session as you would any other PowerShell session.
Manage your projects, references, breakpoints, stack frame locals, menus, toolbars, Visual Studio settings, IDE windows, and even your code from PowerShell scripts, all in a consistent and discoverable way.
Solution Modules - save your StudioShell and IDE customizations as a PowerShell module in your solution, and it will automatically be imported into your StudioShell session when the solution is loaded.
Simple visualization controls you can invoke from the console - create a graph of project code statistics with one line of script.
Fully integrated context-sensitive help.
Host indifference - StudioShell features can be used from any suitable PowerShell host, including NuGet, the standard PowerShell console, and the Integrated Scripting Environment.

For more specific features and examples, please see Examples and Documentation

Demos

A deeply integrated Mercurial file status monitor with two lines of PowerShell:

Launch in another window

Exploring the DTE provider:

Launch in another window

Updated Wiki: Home

beefarino — Mon, 04 Feb 2013 00:52:53 GMT

Overview

Current Release

Getting Involved

There are several ways you can get involved in this project:

Contribute your scripts to the StudioShell.Contrib project.
Use StudioShell and log any issues using the Issue Tracker.
If you are interested in expanding support for the SSMS object model in StudioShell, please contact the project coordinator.
If you are interested in expanding the DTE provider with additional features of the Visual Studio service offering, please contact the project coordinator.

Features

The features supported by StudioShell include:

Support for standard PowerShell profile scripts, as well as StudioShell profile scripts - customize your StudioShell session as you would any other PowerShell session.
Manage your projects, references, breakpoints, stack frame locals, menus, toolbars, Visual Studio settings, IDE windows, and even your code from PowerShell scripts, all in a consistent and discoverable way.
Solution Modules - save your StudioShell and IDE customizations as a PowerShell module in your solution, and it will automatically be imported into your StudioShell session when the solution is loaded.
Simple visualization controls you can invoke from the console - create a graph of project code statistics with one line of script.
Fully integrated context-sensitive help.
Host indifference - StudioShell features can be used from any suitable PowerShell host, including NuGet, the standard PowerShell console, and the Integrated Scripting Environment.

For more specific features and examples, please see Examples and Documentation

Demos

A deeply integrated Mercurial file status monitor with two lines of PowerShell:

Launch in another window

Exploring the DTE provider:

Launch in another window

Updated Wiki: Home

beefarino — Mon, 25 Jun 2012 18:46:02 GMT

Overview

Current Release

Beta

The current beta release of StudioShell is 1.3. For more information, see StudioShell 1.3.

The StudioShell beta is also available as a NuGet package for Visual Studio 2010.

Stable

The current stable release of StudioShell is 1.2. For more information, see StudioShell 1.2.

StudioShell is also available as a NuGet package for Visual Studio 2010.

Kudos

Special thanks to the following software vendors for their help and support in the process leading up to the 1.2 release:

Getting Involved

There are several ways you can get involved in this project:

Use StudioShell and log any issues using the Issue Tracker.
If you are interested in expanding support for the SSMS object model in StudioShell, please contact the project coordinator.
If you are interested in expanding the DTE provider with additional features of the Visual Studio service offering, please contact the project coordinator.

Features

The features supported by StudioShell include:

Support for standard PowerShell profile scripts, as well as StudioShell profile scripts - customize your StudioShell session as you would any other PowerShell session.
Manage your projects, references, breakpoints, stack frame locals, menus, toolbars, Visual Studio settings, IDE windows, and even your code from PowerShell scripts, all in a consistent and discoverable way.
"Solution Modules" - save your StudioShell and IDE customizations as a PowerShell module in your solution, and it will automatically be imported into your StudioShell session when the solution is loaded.
Simple visualization controls you can invoke from the console - create a graph of project code statistics with one line of script.
Fully integrated context-sensitive help.
Host indifference - StudioShell features can be used from any suitable PowerShell host, including NuGet and the standard PowerShell console.

For more specific features and examples, please see Examples and Documentation

Demos

A deeply integrated Mercurial file status monitor with two lines of PowerShell:

Launch in another window

Exploring the DTE provider:

Launch in another window

Updated Wiki: Cmdlet IDE Support Matrix

beefarino — Fri, 27 Jan 2012 22:40:43 GMT

Noun

get-childitem

get-item

new-item

set-item

remove-item

clear-item

move-item

copy-item

rename-item

invoke-item

get-itemproperty

set-itemproperty

get-help

standard path

Root (DTE)

dte:/

Add-In

dte:/addins

Window

Activates the window, making it visible and giving it input focus

dte:/windows

IDE Setting

updates the value of the IDE property

dte:/properties

Window Configuration

defines a new named window configuration based on the current IDE window layout

updates an existing named window configuration using the current IDE window layout

applies a named window configuration to the IDE, rearranging windows as necessary to reproduce the named window state

dte:/windowconfigurations

IDE Command

create a new IDE command that runs a powershell script block, associates key bindings

updates key bindings for the specified command

executes the specified command; works for all IDE commands, including third-party extensions

dte:/commands

IDE Command Bar

creates a new IDE command bar to which you can add popup menus, buttons, and drop-downs

dte:/commandbars

IDE Command Bar Control

adds a new control to an existing command bar; associates buttons with scriptblocks or IDE command

dte:/commandbars/[command bar name]/[control id]

Output Pane

creates a new named output pane and displays it in the IDE

activates the output pane

dte:/outputpanes

Task List Item

creates a new task in the task list

updates the task list item state

clears the task description text

dte:/tasks

Error List Item

creates a new error, warning, or message in the error list

attempts to navigate to the file / location information in the error list item

dte:/errors

Selected Project

dte:/selecteditems/projects

Selected Project Item

dte:/selecteditems/projectitems

Selected Code Model Item

Debugger

dte:/debugger

Breakpoint

deletes the specified breakpoint

disables the specified breakpoint, but does not delete it

enables the specified breakpoint

dte:/debugger/breakpoints

Debugged Process

dte:/debugger/debuggedprocesses

Stack Frame

dte:/debugger/debuggedprocesses/[process name]/[thread id or name]/(current)|[frame index]

Debugged Thread

dte:/debugger/debuggedprocesses/[process name]/[thread id or name]

Frame Argument

dte:/debugger/debuggedprocesses/[process name]/[thread id or name]/(current)|[frame index]/arguments

Local Variable

dte:/debugger/debuggedprocesses/[process name]/[thread id or name]/(current)|[frame index]/locals

Solution

dte:/solution

Project

creates a new project from an existing file or VS template

dte:/solution/projects

Project Item

creates a new project item from an existing file or VS template

opens the default editor for the project item

dte:/solution/projects/[project name]/

Solution Folder

creates a new solution folder

dte:/solution/projects/[project name]/

Project Reference

adds a project, assembly, or com reference to the project

dte:/solution/projects/[project name]/references

Code Model

dte:/solution/projects/[project name]/[project item name]/codemodel

Import (using statement)