VS Command Shell

Source code checked in, #99885

Project Collection Service Accounts — Mon, 01 Oct 2012 21:24:31 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #99884

Project Collection Service Accounts — Mon, 01 Oct 2012 21:16:08 GMT

Checked in by server upgrade

Source code checked in, #74794

_TFSSERVICE — Tue, 03 Aug 2010 19:44:57 GMT

Checked in by server upgrade

Reviewed: 1.2 Production (Nov 24, 2009)

brainslugs83 — Tue, 24 Nov 2009 21:32:58 GMT

Rated 1 Stars (out of 5) - Does not work. If you type any PowerShell commands into the plugin's plain-jane window, visual studio comes crashing down.

New Post: Bugs and comments

brainslugs83 — Tue, 24 Nov 2009 21:31:13 GMT

Is this the place we're piling up bugs?

Here's my 2 cents, the plug-in does nothing.

When I pop up a Shell Window (VSCmdShell) and type in ANY valid powershell commands, visual studio comes crashing down. LAME.

New Post: Bugs and comments

brainslugs83 — Tue, 24 Nov 2009 21:31:13 GMT

Is this the place we're piling up bugs?

Here's my 2 cents, the plug-in does nothing.

When I pop up a Shell Window (VSCmdShell) and type in ANY valid powershell commands, visual studio comes crashing down. LAME.

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.

NEW POST: Termination of child executables when restarting shell.

DannyAsher — Mon, 17 Dec 2007 14:30:10 GMT

Hi,

I noticed than when I started a (long-running) process, restarting the shell would not terminate the spawned process. I think this would be desirable behaviour.

Many thanks,
Daniel

New Post: Termination of child executables when restarting shell.

DannyAsher — Mon, 17 Dec 2007 14:30:10 GMT

Hi,

I noticed than when I started a (long-running) process, restarting the shell would not terminate the spawned process. I think this would be desirable behaviour.

Many thanks,
Daniel

New Post: Termination of child executables when restarting shell.

DannyAsher — Mon, 17 Dec 2007 14:30:10 GMT

Hi,

I noticed than when I started a (long-running) process, restarting the shell would not terminate the spawned process. I think this would be desirable behaviour.

Many thanks,
Daniel

NEW POST: Support For Ctrl-C

DannyAsher — Mon, 17 Dec 2007 14:27:54 GMT

Is there any support for breaking execution with Ctrl-C?

I've tried to use VsCommandShell to spawn the executable for my testing framework, but being unable to terminate a run has made this less, rather than more convenient.

Keep up the good work!

Daniel

New Post: Support For Ctrl-C

DannyAsher — Mon, 17 Dec 2007 14:27:54 GMT

New Post: Support For Ctrl-C

DannyAsher — Mon, 17 Dec 2007 14:27:54 GMT

Project License Changed

Fri, 30 Nov 2007 17:28:01 GMT

Microsoft Public License (Ms-PL) This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software. 1. Definitions The terms "reproduce," "reproduction," "derivative works," and "distribution" have the same meaning here as under U.S. copyright law. A "contribution" is the original software, or any additions or changes to the software. A "contributor" is any person that distributes its contribution under this license. "Licensed patents" are a contributor's patent claims that read directly on its contribution. 2. Grant of Rights (A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce its contribution, prepare derivative works of its contribution, and distribute its contribution or any derivative works that you create. (B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free license under its licensed patents to make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its contribution in the software or derivative works of the contribution in the software. 3. Conditions and Limitations (A) No Trademark License- This license does not grant you rights to use any contributors' name, logo, or trademarks. (B) If you bring a patent claim against any contributor over patents that you claim are infringed by the software, your patent license from such contributor to the software ends automatically. (C) If you distribute any portion of the software, you must retain all copyright, patent, trademark, and attribution notices that are present in the software. (D) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. If you distribute any portion of the software in compiled or object code form, you may only do so under a license that complies with this license. (E) The software is licensed "as-is." You bear the risk of using it. The contributors give no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement.