StudioShell

Created Unassigned: Error upgrading the chocolatey package [62]

zippy1981 — Sun, 09 Jun 2013 22:01:28 GMT

I was doing a cup all from UAC elevated command prompt.

I got the following. I'll try to troubleshoot some more this week.

```
Finished installing 'skype' and dependencies - if errors not shown in console, none detected. Check log for errors if unsure.
Chocolatey (v0.9.8.20) is installing StudioShell and dependencies. By installing you accept the license for StudioShell and each dependency you are installing.
______ StudioShell v1.5.1.2 ______
Write-Error : studioshell did not finish successfully. Boo to the chocolatey gods!
-----------------------
[ERROR] Cannot bind argument to parameter 'Path' because it is null.
-----------------------
At C:\Chocolatey\chocolateyInstall\helpers\functions\Write-ChocolateyFailure.ps1:30 char:2
+ Write-Error $errorMessage
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Error

Join-Path : Cannot bind argument to parameter 'Path' because it is null.
At C:\Chocolatey\lib\StudioShell.1.5.1.2\tools\chocolateyInstall.ps1:34 char:28
+ $settingsSpec = join-path $addInInstallPath -child "UserProfile/settings.txt";
+ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Join-Path], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand

Press Enter or Esc to close console...
```

Commented Issue: Variable names don't autocomplete [60]

beefarino — Sat, 08 Jun 2013 02:47:49 GMT

Subject says all $psver+TAB doesn't work, but $psversiontable+Enter returns something. Also applies to variables I define myself.
Comments: I tested on VS2010 and V2012, win8+PS3 What modules do you have installed?

Commented Issue: Variable names don't autocomplete [60]

zippy1981 — Fri, 07 Jun 2013 09:12:58 GMT

Subject says all $psver+TAB doesn't work, but $psversiontable+Enter returns something. Also applies to variables I define myself.
Comments: I waited 3+ minutes on Windows 7 + PS v3 + Visual Studio 2012 and it didn't work. I'll try windows 8 later What particular VS version did you test on?

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

Commented Issue: Ctrl-C closes Visual Studio [35]

beefarino — Thu, 06 Jun 2013 23:37:15 GMT

When I press Ctrl-C, Visual Studio is immediately closed. Does not seem to happen after closing (using exit) and re-opening the StudioShell console, but then Ctrl-C does not work at all.
Comments: Is this issue still active for you? I have not been able to replicate this behavior (nor has anyone else I've asked)...

Closed Issue: Studio Shell 1.2 (SSMS) - SSMS Application Crashed when exiting 'Old School' console. [30]

beefarino — Thu, 06 Jun 2013 23:35:40 GMT

I got surpised that you close this issue. So, the feedback is: I would suggest to remove the "Old School" option until you figured out that it can be fix. StudioShell is pretty stable without it, and should be enough for a DBA and/or SQL Developer to work with it. I got my issue resolved with my Start-Demo function, and I looking forward to us it next week.

I go it installed in SSMS 2012 RC0,and I'm loving it!! I have to admit this application does have potential.

Thanks,
Max
Comments: The old school console remains as a "use at your own risk" feature.

Edited Issue: Running an interactive cmd.exe shell from inside StudioShell breaks StudioShell [34]

beefarino — Thu, 06 Jun 2013 23:34:19 GMT

If I type cmd.exe in StudioShell I don't get a cmd prompt. I can't kill it, even via a pipeline reset or killing the cmd.exe instance from task manager. Couple this with Work item 32, and I have to restart Visual Studio

Closed Issue: Running an interactive cmd.exe shell from inside StudioShell breaks StudioShell [34]

beefarino — Thu, 06 Jun 2013 23:34:19 GMT

Commented Issue: DTE PSdrive and $dte variable not available [46]

beefarino — Thu, 06 Jun 2013 23:32:47 GMT

I have isntalled StudioShell 1.5.0.1 on win8 + VS2012.
I have set the execution policy to RemoteSigned and I'm running VS as admnistrator.
I having an issue accesing the $dte variable and the DTE PSDrive.
They are not available, $dte is empty and the PSDRIVE is not listed (No PSPRovider as well)
I tried to install it on a win7 + VS2012 and vs2010.
I ahve access to DTE and $dte on VS2010 but not on VS2012.

Anyone else has the same issue?

Comments: The 1.5.1 release is much more stable with regards to the nuget install. Please give it a shot and let me know if I can close this issue.

Commented Feature: Make the NuGet package install with Chocolatey [41]

beefarino — Thu, 06 Jun 2013 23:31:17 GMT

It took me a while to realize the reason why cinst StudioShell was not working was that this was actually a vanilla nuget package. It should also have a tools\chocolateyInstall.ps1
Comments: feature added in changeset 2d3ecc54157e

Edited Feature: Make the NuGet package install with Chocolatey [41]

beefarino — Thu, 06 Jun 2013 23:31:17 GMT

It took me a while to realize the reason why cinst StudioShell was not working was that this was actually a vanilla nuget package. It should also have a tools\chocolateyInstall.ps1

Edited Issue: Autocomplete should un-highlight after it fails to match [59]

beefarino — Thu, 06 Jun 2013 23:22:58 GMT

When you invoke autocomplete with a tab it highlights what it is auto completing. As a visual clue that autocomplete has finished with a failure, the highlighting should be removed.

Commented Issue: Autocomplete should un-highlight after it fails to match [59]

beefarino — Thu, 06 Jun 2013 23:22:20 GMT

When you invoke autocomplete with a tab it highlights what it is auto completing. As a visual clue that autocomplete has finished with a failure, the highlighting should be removed.
Comments: fixed in changeset 8ceae56276a1.

Source code checked in, #7ed4ebf5b4a5

jim christopher — Thu, 06 Jun 2013 23:18:58 GMT

fixed default value of RunStudioShellOnStartup setting so that it's really really off. really. For realsies.

Source code checked in, #8ceae56276a1

jim christopher — Thu, 06 Jun 2013 23:05:23 GMT

fixed issue where a failed tab completion leaves the user input hilighted

Commented Issue: Autocomplete should un-highlight after it fails to match [59]

beefarino — Thu, 06 Jun 2013 22:53:36 GMT

Edited Issue: Autocomplete should un-highlight after it fails to match [59]

beefarino — Thu, 06 Jun 2013 22:53:35 GMT

When you invoke autocomplete with a tab it highlights what it is auto completing. As a visual clue that autocomplete has finished with a failure, the highlighting should be removed.

Commented Issue: Variable names don't autocomplete [60]

beefarino — Thu, 06 Jun 2013 22:44:54 GMT

Subject says all $psver+TAB doesn't work, but $psversiontable+Enter returns something. Also applies to variables I define myself.
Comments: I'm trying to replicate this on my win8 box with PS3, but variable completion works. One thing to note about V3 is that the autoloading "feature" causes a big slowdown in completion, especially at startup. Can you try typing $ps + TAB and then leave it for a few minutes? I know I know, but give it a shot and let me know...

Edited Feature: Add an option to start StudioShell on Visual Studio Startup [58]

beefarino — Sat, 01 Jun 2013 13:19:34 GMT

It takes a while to start StudioShell. It would be preferable if I could chose to make that happen at Visual Studio Startup.

Commented Feature: Add an option to start StudioShell on Visual Studio Startup [58]

beefarino — Sat, 01 Jun 2013 13:19:34 GMT

It takes a while to start StudioShell. It would be preferable if I could chose to make that happen at Visual Studio Startup.
Comments: Just pushed changeset 51ec9b2f5c91 with this added feature. Will fold into the next release cycle.