VSCmdShell Wiki & Documentation Rss Feed

UPDATED WIKI: Home

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

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

bertanaygun — Tue, 08 May 2007 16:22:32 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.

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

bertanaygun — Tue, 08 May 2007 16:22:21 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.

Check out all of the VSCmdShell Features for the 1.1 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 WIKI: Home

JohnDAddamio — Mon, 13 Nov 2006 21:48:22 GMT

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.

Check out all of the VSCmdShell Features for the 1.1 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

Unzip VSCmdShell 1.1 Release.zip
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.2 release. Check out the current work items at 1.2 Alpha.

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 WIKI: Building VSCmdShell

JohnDAddamio — Mon, 13 Nov 2006 20:28:45 GMT

Building VSCmdShell

We recently made some changes to the build configurations for VSCmdShell. To build the Debug configuration, no additional tools are required. This way you can build and experiment with the source code more easily. The Debug configuration does not build test projects.

If you wish to contribute changes to the VSCmdShell project, you must build the Debug-Test, FxCop-Release and Release configurations. You will need to use the tools and procedures described below to build those configurations:

VSCmdShell requires additional tools to be installed in order to build:

Code analysis is performed by FxCop 1.35 RC 1, which is available at http://www.gotdotnet.com/team/fxcop/
Unit tests are developed and run using NUnit 2.2.7, which is available at http://www.nunit.org
The installer is built with WiX 2.0.3719, which is available at http://sourceforge.net/projects/wix/
Building VSCmdShell requires Microsoft PowerShell, which is available at http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx

Step 0:
Download the tools listed above.

Step 1:
Download the latest sources on the Source Code page

Step 2:
Open the VSCmdShell.Settings.targets file. This file is located in the solution directory.

You will find the following tags for each of the tools listed above:
<FxCopExtDir> </FxCopExtDir>
<NUnitDir> </NUnitDir>
<WiXDir> </WiXDir>

Step 3:
Set these properties to the tools' installation directories. Be sure to include a trailing slash in each path.

For example:
<WiXDir>C:\tools\WiX\2.0.3719\</WiXDir>

Step 4:
Close and reopen the solution, when inside the VS IDE, to pick up the new tool locations.

Step 5:
Build.

Once solution is successfully built, MSI package will be placed under CommandShell\VSCmdShell Installer directory.

UPDATED WIKI: Home

JohnDAddamio — Mon, 13 Nov 2006 20:20:41 GMT

Welcome to the VS Command Shell Homepage!

Unzip VSCmdShell 1.1 Release.zip
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.2 release. Check out the current work items at 1.2 Alpha.

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

bertanaygun — Mon, 11 Sep 2006 23:10:47 GMT

Welcome to the VS Command Shell Homepage!

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

Quick Start to using VS Command Shell

Unzip VSCmdShell 1.1 Release.zip
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.2 release. Check out the current work items at 1.1 Alpha.

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

bertanaygun — Mon, 11 Sep 2006 23:10:26 GMT

Welcome to the VS Command Shell Homepage!

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

Quick Start to using VS Command Shell

Unzip VSCmdShell 1.1 Release.zip
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.1 release. Check out the current work items at 1.1 Alpha.

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

bertanaygun — Mon, 11 Sep 2006 23:09:56 GMT

Welcome to the VS Command Shell Homepage!

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

Quick Start to using VS Command Shell

Unzip VSCmdShell 1.0 Release.zip
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.1 release. Check out the current work items at 1.1 Alpha.

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 WIKI: VSCmdShell Features

bertanaygun — Mon, 11 Sep 2006 23:09:35 GMT

The 1.0 version of VSCmdShell provides

Hosting of Windows Command Shell (cmd.exe) and Windows PowerShell in a Visual Studio tool window
Customization options presented under Tools - Options - Power Toys
Extensibility support to host other shells within VSCmdShell - refer to the design doc (found in any source code download) for more information.

New features in 1.1 version of VSCmdShell are:

Better auto completion of filenames.
Ability to restart VSCmdShell session
Ability to determine starting directory based on number of choices such as current project directory, current solution directory or a custom choice.

UPDATED WIKI: Home

JoshLedgard — Wed, 16 Aug 2006 23:14:04 GMT

Welcome to the VS Command Shell Homepage!

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

Quick Start to using VS Command Shell

Unzip VSCmdShell 1.0 Release.zip
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.1 release. Check out the current work items at 1.1 Alpha.

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

JoshLedgard — Wed, 16 Aug 2006 23:13:34 GMT

Welcome to the VS Command Shell Homepage!

Check out all of the VSCmdShell Features for the 1.0 release.
Quick Start to using VS Command Shell

Unzip VSCmdShell 1.0 Release.zip
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.1 release. Check out the current work items at 1.1 Alpha.

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

JoshLedgard — Wed, 16 Aug 2006 23:10:36 GMT

Welcome to the VS Command Shell Homepage!

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

Quick Start to using VS Command Shell

Unzip VSCmdShell 1.0 Release.zip
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.1 release. Check out the current work items at 1.1 Alpha.

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

saraford — Mon, 17 Jul 2006 20:29:22 GMT

!!! 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 [url:Windows PowerShell|http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx]. Check out all of the [608] for the 1.0 release. *Quick Start to using VS Command Shell* # Unzip [url:VSCmdShell 1.0 Release.zip|http://www.codeplex.com/Project/FileDownload.aspx?ProjectName=VSCmdShell&DownloadId=566] # 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 ## [url:FXCop 1.35 RC 1|http://www.gotdotnet.com/team/fxcop/] ## [url:NUnit 2.2.7|http://www.nunit.org] ## [url:WiX 2.0.3719|http://sourceforge.net/projects/wix/] ## [url:Windows PowerShell RC1|http://www.microsoft.com/downloads/details.aspx?FamilyId=2B0BBFCD-0797-4083-A817-5E6A054A85C9&displaylang=en] # [url:Download the latest source code|http://www.codeplex.com/SourceControl/ListDownloadableCommits.aspx?ProjectName=VSCmdShell] # Steps for [609] # Steps for [610] *Contributing to VSCmdShell* We're looking for developers to join us in the 1.1 release. Check out the current work items at [release:109]. 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 [file:Project Assignment Agreement.TIF] form and follow the [611] to send it to us. Note that by posting your submission to the Issue Tracker, you agree to do so under the [url:CodePlex TOU|http://www.codeplex.com/Legal/terms.aspx] *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 [url:forums|http://www.codeplex.com/Project/ListForums.aspx?ProjectName=VSCmdShell] * [url:Submit issues or feature suggestions|http://www.codeplex.com/WorkItem/List.aspx?ProjectName=VSCmdShell] * Fix bugs or check in new features - see above section

UPDATED WIKI: VSCmdShell Assignment Agreement Instructions

saraford — Mon, 17 Jul 2006 20:17:28 GMT

Thank you for your interest in contributing to the VSCmdShell project. In order to have your contributions included in future versions of VSCmdShell, you need to fill out the assignment form covering your contributions. Please print a hard copy of the Project Assignment Agreement posted on the VSCmdShell homepage, fill it out, and return the signed original to: CWC VSCmdShell Project Microsoft Corporation One Microsoft Way Redmond, WA 98052 Instructions for filling out the Assignment Agreement: In the title of the agreement, before "Assignment Agreement," please enter "VSCmdShell" In initial paragraph, please enter your full legal name in the space labeled "You" In paragraph #1, please enter "VSCmdShell" in the space labeled "Project" At the bottom of the agreement, please fill in your full legal name, signature and date on the designated lines at the end of the agreement. Please be sure to enter the date of your signature on the line labeled Date, below the signature line. If authorization is required from any entity other than you, the individual, please have authorized representatives from the entity(s) complete the Name, Signature, By, Title and Date lines in the spaces provided below your own signature. If you have any questions regarding this assignment agreement or how to fill it out, please contact [url:Sara Ford|http://blogs.msdn.com/saraford/contact.aspx].

UPDATED WIKI: VSCmdShell Assignment Agreement Instructions

saraford — Mon, 17 Jul 2006 20:16:56 GMT

Thank you for your interest in contributing to the MSBee project. In order to have your contributions included in future versions of MSBee, you need to fill out the assignment form covering your contributions. Please print a hard copy of the Project Assignment Agreement posted on the MSBee homepage, fill it out, and return the signed original to: CWC MSBee Project Microsoft Corporation One Microsoft Way Redmond, WA 98052 Instructions for filling out the Assignment Agreement: In the title of the agreement, before "Assignment Agreement," please enter "VSCmdShell" In initial paragraph, please enter your full legal name in the space labeled "You" In paragraph #1, please enter "VSCmdShell" in the space labeled "Project" At the bottom of the agreement, please fill in your full legal name, signature and date on the designated lines at the end of the agreement. Please be sure to enter the date of your signature on the line labeled Date, below the signature line. If authorization is required from any entity other than you, the individual, please have authorized representatives from the entity(s) complete the Name, Signature, By, Title and Date lines in the spaces provided below your own signature. If you have any questions regarding this assignment agreement or how to fill it out, please contact [url:Sara Ford|http://blogs.msdn.com/saraford/contact.aspx].

UPDATED WIKI: Home

saraford — Mon, 17 Jul 2006 20:09:31 GMT

!!! 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 [url:Windows PowerShell|http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx]. Check out all of the [608] for the 1.0 release. *Quick Start to using VS Command Shell* # Unzip [url:VSCmdShell 1.0 Release.zip|http://www.codeplex.com/Project/FileDownload.aspx?ProjectName=VSCmdShell&DownloadId=566] # 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 ## [url:FXCop 1.35 RC 1|http://www.gotdotnet.com/team/fxcop/] ## [url:NUnit 2.2.7|http://www.nunit.org] ## [url:WiX 2.0.3719|http://sourceforge.net/projects/wix/] ## [url:Windows PowerShell RC1|http://www.microsoft.com/downloads/details.aspx?FamilyId=2B0BBFCD-0797-4083-A817-5E6A054A85C9&displaylang=en] # [url:Download the latest source code|http://www.codeplex.com/SourceControl/ListDownloadableCommits.aspx?ProjectName=VSCmdShell] # Steps for [609] # Steps for [610] *Contributing to VSCmdShell* We're looking for developers to join us in the 1.1 release. Check out the current work items at [release:109]. 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 [file:Project Assignment Agreement.TIF] form and follow the [611] to send it to us. Note that by posting your submission to the Issue Tracker, you agree to do so under the [url:CodePlex TOU|http://www.codeplex.com/Legal/terms.aspx] *Join the Community* There are numerous ways you can participate in the MSBee community * Blog about VSCmdShell * Ask and answer questions regarding VSCmdShell on the [url:forums|http://www.codeplex.com/Project/ListForums.aspx?ProjectName=VSCmdShell] * [url:Submit issues or feature suggestions|http://www.codeplex.com/WorkItem/List.aspx?ProjectName=VSCmdShell] * Fix bugs or check in new features - see above section

UPDATED WIKI: Building VSCmdShell

bertanaygun — Mon, 17 Jul 2006 19:59:22 GMT

!!! Building VSCmdShell VSCmdShell requires additional tools to be installed in order to build: # Code analysis is performed by FxCop 1.35 RC 1, which is available at [url:http://www.gotdotnet.com/team/fxcop/] # Unit tests are developed and run using NUnit 2.2.7, which is available at [url:http://www.nunit.org] # The installer is built with WiX 2.0.3719, which is available at [url:http://sourceforge.net/projects/wix/] # Building VSCmdShell requires Microsoft PowerShell, which is available at [url:http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx] *Step 0:* Download the tools listed above. *Step 1:* Download the latest sources on the [url:Source Code page|http://www.codeplex.com/SourceControl/ListDownloadableCommits.aspx?ProjectName=VSCmdShell] *Step 2:* Open the VSCmdShell.Settings.targets file. This file is located in the solution directory. You will find the following tags for each of the tools listed above: *Step 3:* Set these properties to the tools' installation directories. *Be sure to include a trailing slash in each path.* For example: C:\tools\WiX\2.0.3719\ *Step 4:* Close and reopen the solution, when inside the VS IDE, to pick up the new tool locations. *Step 5:* Build. Once solution is successfully built, MSI package will be placed under CommandShell\VSCmdShell Installer directory.

UPDATED WIKI: Running Verification Scripts

bertanaygun — Mon, 17 Jul 2006 19:59:02 GMT

!!! Running the provided build and test scripts VSCmdShell contains scripts for building and testing modifications to the source code. You can find these scripts under the *Verification Scripts* folder. To perform a build, run the following from the command prompt {{ build.cmd [612] [613] }} * clean and rebuild are the build types * debug, release, fxcop-debug, and fxcop-release are the different build configurations. ** debug and release configurations build VSCmdShell and then build and run its installer. ** The FxCop configurations build VSCmdShell and then run FxCop on its assemblies. To run a VSCmdShell test pass, run the following from the command prompt {{ runtests.cmd [614] }} * runtests.cmd runs the VSCmdShell unit tests. More information is available in the VSCmdShellTestPlan.doc under the *doc* folder.