VSCmdShell Work Item Rss Feed

Commented Issue: In x64 Vista and VS2008 the command shell does not launch cmd.exe

mattgollob — Fri, 06 Feb 2009 23:32:16 GMT

In the above mentioned config, the command shell is empty and does not shouw up the cmd prompt. The powershell seems to work fine. After the first command is entered it just hangs VS
Comments: ** Comment from web user: mattgollob **

I realize this issue is quite old, but I ran into it myself and I think I may know what the problem is. In my case, it was because I had only VS2008 installed, and when the CommandShellHost is initialized it attempts to read *VS2005's* InstallDir registry value when building the path to vsvars32.bat. Changing line 123 in CommandShell/CommandShellHost.cs from:

RegistryKey rk = Registry.LocalMachine.OpenSubKey("SOFTWARE\\Microsoft\\VisualStudio\\8.0");

to:
RegistryKey rk = Registry.LocalMachine.OpenSubKey("SOFTWARE\\Microsoft\\VisualStudio\\9.0");

This single change resolved the issue for me. Based on this, I don't believe that this issue is related to Vista, nor is it related to x64.

Note in the source there is a big "//HACK:" comment indicating that this logic needs refactoring. That is something I intend to do in the next few days / weeks

Commented Issue: Invalid operation exception with VS2008RTM

EyalShilony — Fri, 27 Jun 2008 08:55:44 GMT

Freshly installed XPSP2, VS2008ProRTM, VSSDK, MSDN for VS2008, PlatformSDK6.1
Installed VS Command Shell.
In shell: !Help.About
Close Help|About with OK button.
*twiddle*
"Microsoft Visual Studio has encountered a problem ..."

Details say it's an invalid operation exception in microsoft.powertoys.vscmdshell
Comments: ** Comment from web user: EyalShilony **

Hello,

It's awesome add-in and I wish I can use it for VS2008. :)

I installed the add-in myself and whenever I'm trying to use it (using the default setting) I'm getting the following exception.

System.InvalidOperationException was unhandled
Message="Operation is not valid due to the current state of the object."
Source="Microsoft.VSPowerToys.VSCmdShell"
StackTrace:
at Microsoft.VSPowerToys.VSCmdShell.Hosts.CommandShellHost.get_InputStream()
at Microsoft.VSPowerToys.VSCmdShell.Hosts.CommandShellHost.ExecuteCommand(String command)
at Microsoft.VSPowerToys.VSCmdShell.ShellTextBox.IssueCommand()
at Microsoft.VSPowerToys.VSCmdShell.ShellTextBox.HandleKeyPressEvent(Object sender, KeyPressEventArgs e)
at System.Windows.Forms.Control.OnKeyPress(KeyPressEventArgs e)
at System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
at System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
at System.Windows.Forms.Control.WmKeyChar(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.TextBoxBase.WndProc(Message& m)
at System.Windows.Forms.RichTextBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ActiveXImpl.System.Windows.Forms.IWindowTarget.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
InnerException:

Regards.

Created Issue: VS2008 Exception: System.InvalidOperationException

EyalShilony — Fri, 27 Jun 2008 08:52:51 GMT

Hello,

COMMENTED ISSUE: In x64 Vista and VS2008 the command shell does not launch cmd.exe

bamueller — Fri, 02 May 2008 20:02:38 GMT

I am running Windows Server 2008 (x64) and VS 2008. I can click on the VSCmdShell, but it appears empty (blank) and as soon as I press the "enter" key within the blank window, I get a fatal VS error that causes a reset.

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: devenv.exe
Problem Signature 02: 9.0.21022.8
Problem Signature 03: 47317b3d
Problem Signature 04: Microsoft.VSPowerToys.VSCmdShell
Problem Signature 05: 1.1.0.0
Problem Signature 06: 474df095
Problem Signature 07: 9f
Problem Signature 08: 19
Problem Signature 09: System.InvalidOperationException
OS Version: 6.0.6001.2.1.0.274.10
Locale ID: 1033

Additional information about the problem:
LCID: 1033

CREATED ISSUE: Invalid operation exception with VS2008RTM

glundberg — Fri, 07 Mar 2008 08:03:13 GMT

CREATED ISSUE: In x64 Vista and VS2008 the command shell does not launch cmd.exe

pmural1 — Sun, 06 Jan 2008 23:11:36 GMT

In the above mentioned config, the command shell is empty and does not shouw up the cmd prompt. The powershell seems to work fine. After the first command is entered it just hangs VS

CREATED ISSUE: In VS2008, VSCmdShell opens cmd.exe with the VS2005 environment

hognef — Fri, 21 Dec 2007 10:40:27 GMT

I have both VS2005 and VS2008 installed, and VSCmdShell works fine in both, except the cmd.exe prompt in VS2008 loads the VS2005 environment, instead of the VS2008 environment. This appears to be hardcoded (I've had a look at the source code).

A solution could be based on the fact that the DTE object exposes a member, Version, which should return "8.0" when running under VS2005 and "9.0" when running under VS2008. This could be used to load the correct environment depending on Visual Studio version.

CLOSED ISSUE: Does not install with only VS2008 installed on system

bertanaygun — Thu, 29 Nov 2007 02:02:25 GMT

I have only VS2005 express and VS2008 "orcas" beta2 installed. Installer refuses to install VS Command Shell.
Comments: This issue is fixed with the new release.

CREATED ISSUE: Does not install with only VS2008 installed on system

ozz — Mon, 01 Oct 2007 02:05:34 GMT

I have only VS2005 express and VS2008 "orcas" beta2 installed. Installer refuses to install VS Command Shell.

CREATED ISSUE: Shell host loading error

DannyAsher — Mon, 20 Aug 2007 15:27:40 GMT

Error: Assembly C;\Program Files\Power Toys for Visual Studio\Microsoft.VSPowerToys.VSCmdShell.PowerShellHost.dll could not be loaded. Error was: \nAssembly could not be loaded because of an unknown error.

Also version number is given as 1.1 in the Addins Manager dialog.

Best of luck fixing these...

COMMENTED ISSUE: VSCmdShell crashes Visual Studio, no error message

DannyAsher — Wed, 04 Jul 2007 10:44:17 GMT

OK, so here's the deal:
I installed VSCmdShell and tried to get it to work with Windows Powershell. For some reason, Powershell wasn't showing up in the list of available shells. So, I selected browse for shell and tried each of the 3 DLLs that are recognized by VSCmdShell in the powershell directory. Each one gave me a failure. So I exited VS and when I restarted it and went to goto options (to switch vscmdshell to cmd.exe) VS 2005 crashed to the desktop with no errors, and nothing in the event viewer. I uninstalled VSCmdShell and even tried removing all references to it in the registry. After uninstall, "Power Toys" does not show up in my "options" dialog box. When I reinstall it, "Power Toys" DOES show up. But it STILL crashes. Where is it saving this corrupted data?(i think its trying to load the wrong shell) because I cannot reset it! I attached the debugger to VS 2005 before I crashed it by trying to change the powertoys options. Except for the "symbols not found" messages, below is the output from the debugger:

A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll
A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll
'devenv.exe' (Managed): Loaded 'eelfkubc', No symbols loaded.
A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll
'devenv.exe' (Managed): Loaded 'qr6ihisx', No symbols loaded.
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VSPowerToys.VSCmdShell.dll
A first chance exception of type 'System.OutOfMemoryException' occurred in System.Windows.Forms.dll
The program '[1184] devenv.exe: Managed' has exited with code -1073741795 (0xc000001d).
Comments: ** Comment from web user: DannyAsher **

I get similar behaviour as Simon Ams, i.e. the error message "Assembly C:\Program Files\Power Toys for Visual Studio\VSCmdShell\Microsoft.VSPowerToys.VSCmdShell.PowerShellHost.dll could not be loaded. Error was: \nAssembly could not be loaded because of an unknown error."

I could not find a user.config file in %AppData% but did notice that
<Addin>
<FriendlyName>VSCmdShell 1.1</FriendlyName>

was incorrect.

I'm using VS2005 Team Edition for Software Devs with SP1

COMMENTED ISSUE: VSCmdShell crashes Visual Studio, no error message

simon_ams — Tue, 12 Jun 2007 06:37:15 GMT

OK, so here's the deal: I installed VSCmdShell and tried to get it to work with Windows Powershell. For some reason, Powershell wasn't showing up in the list of available shells. So, I selected browse for shell and tried each of the 3 DLLs that are recognized by VSCmdShell in the powershell directory. Each one gave me a failure. So I exited VS and when I restarted it and went to goto options (to switch vscmdshell to cmd.exe) VS 2005 crashed to the desktop with no errors, and nothing in the event viewer. I uninstalled VSCmdShell and even tried removing all references to it in the registry. After uninstall, "Power Toys" does not show up in my "options" dialog box. When I reinstall it, "Power Toys" DOES show up. But it STILL crashes. Where is it saving this corrupted data?(i think its trying to load the wrong shell) because I cannot reset it! I attached the debugger to VS 2005 before I crashed it by trying to change the powertoys options. Except for the "symbols not found" messages, below is the output from the debugger: A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll 'devenv.exe' (Managed): Loaded 'eelfkubc', No symbols loaded. A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll 'devenv.exe' (Managed): Loaded 'qr6ihisx', No symbols loaded. A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VSPowerToys.VSCmdShell.dll A first chance exception of type 'System.OutOfMemoryException' occurred in System.Windows.Forms.dll The program '[1184] devenv.exe: Managed' has exited with code -1073741795 (0xc000001d). Comments: ** Comment from web user: simon_ams **

Same thing happened to me when I tried selecting the Microsoft.VSPowerToys.VSCmdShell.Interfaces.dll assembly as the selected shell.

The suggested Microsoft.VSPowerToys.VSCmdShell.PowerShellHost.dll assembly does not work.
I get the error message:
Assembly C:\Program Files\Power Toys for Visual Studio\VSCmdShell\Microsoft.VSPowerToys.VSCmdShell.PowerShellHost.dll could not be loaded. Error was: \nAssembly could not be loaded because of an unknown error.

CLOSED ISSUE: PowerShellHost is not compatible with PowerShell RC2

mattgollob — Sat, 05 May 2007 23:26:08 GMT

Current PowerShell host is only compatible with RC1 release of PowerShell. If a user has RC2 installed, PowerShellHost could not be loaded due to interface changes.

COMMENTED ISSUE: PowerShellHost is not compatible with PowerShell RC2

mattgollob — Sat, 05 May 2007 23:26:02 GMT

Current PowerShell host is only compatible with RC1 release of PowerShell. If a user has RC2 installed, PowerShellHost could not be loaded due to interface changes. Comments: ** Comment from web user: mattgollob **

Resolved with changeset 21977.

CLOSED ISSUE: VS Command "Intellisense" turns off if you mistype

mattgollob — Sat, 05 May 2007 23:19:58 GMT

If you are using a VS command from the command shell and you type a string that doesn’t fit with the “intellisense” style pop-up to the point that the pop-up goes away, backspacing does not bring the intellisense window back. The desired behavior is that it should. For example, if I type: !File.Open3 …the Intellisense window will be open until I hit the “3” key, and then it will go away. If I hit backspace, the window won’t re-popup unless I go back to the beginning of the line and enter an “!” again.

COMMENTED ISSUE: PowerShellHost is not compatible with PowerShell RC2

stimpy77 — Wed, 02 May 2007 18:00:09 GMT

Same seems to be true of PowerShell RTM!! This is RTM, guys, RTM has been out for months now.

CLOSED ISSUE: Race condition in CommandShellHost when shell is restarted

mattgollob — Sat, 14 Apr 2007 21:57:43 GMT

When the CommandShellHost (cmd.exe) is restarted (or when switching from CommandShellHost to PowerShellHost), a race condition develops around asynchronous I/O for stderr and stdout. Steps to reproduce: Scenario 1 (Restart CommandShellHost): 1. Start the VsCmdShell Window using the cmd.exe shell. 2. Right-click in the VsCmdShellWindow and choose "Restart Shell" from the context menu. Scenario 2 (Switch to a different IShellHost implementation, like PowerShellHost): 1. Start the VsCmdShell Window using the cmd.exe shell, or switch to the cmd.exe. 2. Right-click in the VsCmdShellWindow and choose "Options". 3. In the Power Toys/VsCmdShell section, change the "Shell Selection" dropdown to a host other than "Windows Command Shell (cmd.exe)". 4. Click OK on the Options Dialog. 5. Dismiss the VSCmdShell message box instructing you to restart the shell for the change to take effect. 6. Right-click in the VsCmdShell window and choose "Restart Shell" In either scenario, the CPU will race in the devenv.exe process. Setting breakpoints in CommandShellHost.ErrorBeginRead(), CommandShellHost.OutputBeginRead(), CommandShellHost.OnErrorInput() and CommandShellHost.OnOutputInput() will reveal an extremely tight call loop that is causing the race condition.

REOPENED ISSUE: Race condition in CommandShellHost when shell is restarted

mattgollob — Sat, 14 Apr 2007 19:44:21 GMT

Needs to be assigned to a release

COMMENTED ISSUE: Race condition in CommandShellHost when shell is restarted

mattgollob — Sat, 14 Apr 2007 19:44:20 GMT

CLOSED ISSUE: Race condition in CommandShellHost when shell is restarted

mattgollob — Sat, 14 Apr 2007 08:31:22 GMT