VS Command Shell

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

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: bamueller **

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: 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

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.

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.

UPDATED WIKI: Home

bertanaygun — Wed, 28 Nov 2007 23:07:03 GMT

News Feeds

Welcome to the VS Command Shell Homepage!

VSCmdShell provides users with a shell window inside the Visual Studio IDE that can be used for Visual Studio commands as well. Current version allows user to use either Windows Command Shell (cmd.exe) or Windows PowerShell.

NOTE: The VS Cmd Shell is an Add-In tool. Therefore, it will not work with Express editions of Visual Studio 2005. It does work with Standard or higher editions of VS 2005.

10/08/2007: VSCmdShell 1.2 release is updated to work with Windows Powershell RTM version.
11/27/2007: VSCmdShell 1.2 release is updated to work with Visual Studio 2008 as well.

Check out all of the VSCmdShell Features for the 1.2 release.

Note: We have limited availability of developer time. If someone is interested in debugging and fixing one or more of the bugs reported under Issue Tracker, it would shorten the time between releases.

Quick Start to using VS Command Shell

Download VSCmdShell 1.2 release
Run VSCmdShell.msi to install
Launch Visual Studio 2005
Go to View - Shell Window (VSCmdShell) to open the VS Command Shell tool window

Go to Tools - Options - Power Toys - VSCmdShell for customization options

Getting Started with VSCmdShell Development

Install the following development tools

Contributing to VSCmdShell

We're looking for developers to join us in the 1.3 release. Check out the current work items at 1.2 Production.

Feel free to contribute by

Either creating new or finding existing bugs or feature requests you want to work on
Leave a note in the comments that you're going to investigate this bug (until you have developer rights, you won't be able to assign bugs to yourself)
Download the latest sources and create a bug fix
Zip up your changes and post them as an attachment to the work item
Fill out the Project Assignment Agreement.TIF form and follow the VSCmdShell Assignment Agreement Instructions to send it to us.

Note that by posting your submission to the Issue Tracker, you agree to do so under the CodePlex TOU

Join the Community

There are numerous ways you can participate in the VSCmdShell community

Blog about VSCmdShell
Ask and answer questions regarding VSCmdShell on the forums
Submit issues or feature suggestions
Fix bugs or check in new features - see above section

UPDATED RELEASE: 1.2 Production (May 08, 2007)

Wed, 28 Nov 2007 23:06:24 GMT

The VSCmdShell 1.2 release will contain bug fixes.

*10/08/2007:* Release is updated to work with Windows Powershell RTM.
*11/27/2007:* Release is updated to work with Visual Studio 2008 as well.

Source code checked in

bertanaygun — Wed, 28 Nov 2007 23:01:32 GMT

Making installer compatible with Visual Studio 2008

UPDATED RELEASE: 1.2 Production (May 08, 2007)

Tue, 09 Oct 2007 02:19:41 GMT

The VSCmdShell 1.2 release will contain bug fixes.

*10/08/2007:* Release is updated to work with Windows Powershell RTM.

UPDATED WIKI: Home

bertanaygun — Tue, 09 Oct 2007 02:18:58 GMT

News Feeds

Welcome to the VS Command Shell Homepage!

VSCmdShell provides users with a shell window inside the Visual Studio IDE that can be used for Visual Studio commands as well. Current version allows user to use either Windows Command Shell (cmd.exe) or Windows PowerShell.

NOTE: The VS Cmd Shell is an Add-In tool. Therefore, it will not work with Express editions of Visual Studio 2005. It does work with Standard or higher editions of VS 2005.

10/08/2007: VSCmdShell 1.2 release is updated to work with Windows Powershell RTM version.

Check out all of the VSCmdShell Features for the 1.2 release.

Note: We have limited availability of developer time. If someone is interested in debugging and fixing one or more of the bugs reported under Issue Tracker, it would shorten the time between releases.

Quick Start to using VS Command Shell

Download VSCmdShell 1.2 release
Run VSCmdShell.msi to install
Launch Visual Studio 2005
Go to View - Shell Window (VSCmdShell) to open the VS Command Shell tool window

Go to Tools - Options - Power Toys - VSCmdShell for customization options

Getting Started with VSCmdShell Development

Install the following development tools

Contributing to VSCmdShell

We're looking for developers to join us in the 1.3 release. Check out the current work items at 1.2 Production.

Feel free to contribute by

Either creating new or finding existing bugs or feature requests you want to work on
Leave a note in the comments that you're going to investigate this bug (until you have developer rights, you won't be able to assign bugs to yourself)
Download the latest sources and create a bug fix
Zip up your changes and post them as an attachment to the work item
Fill out the Project Assignment Agreement.TIF form and follow the VSCmdShell Assignment Agreement Instructions to send it to us.

Note that by posting your submission to the Issue Tracker, you agree to do so under the CodePlex TOU

Join the Community

There are numerous ways you can participate in the VSCmdShell community

Blog about VSCmdShell
Ask and answer questions regarding VSCmdShell on the forums
Submit issues or feature suggestions
Fix bugs or check in new features - see above section

UPDATED RELEASE: 1.2 Production (May 08, 2007)

Tue, 09 Oct 2007 02:17:36 GMT

The VSCmdShell 1.2 release will contain bug fixes.

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.

NEW POST: Problem setting PowerShell in Options dialog

stimpy77 — Mon, 03 Sep 2007 19:50:12 GMT

Thinking a couple months retrospectively... umm.. I think I removed the WiX references since I wasn't trying to run the installer but was going to xcopy the DLLs. I'd had WiX installed but it was a different version. StoneFree, if you can manage to clean that out you should be able to get it to compile for you.

NEW POST: Problem setting PowerShell in Options dialog

StoneFree — Mon, 03 Sep 2007 14:50:24 GMT

Hi Stan,

How did you get it to compile? I don't have a lib directory under "Windows Installer XML\bin" and so the build cannot find wixui_featuretree.wixlib.

Where did you find these files as I have downloaded the WIX MSI file and Binaries ZIP, and neither contain it.

Peter

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...