Visual Studio and .NET Framework Home
VS2010 Command Prompt from Tools menu
as Not Reproducible
5/26/2009 8:47:36 AM
User(s) can reproduce this bug
The title of the entry in the tools menu to start the VS 2010 Command prompt is wrong. Also the script runs without first executing an @echo off
Visual Studio 2010 Beta 1
Windows 7 RC
Operating System Language
Steps to Reproduce
Open the tools menu
Click the VS Command Prompt
VS Command Prompt is called "Visual Studio 2008 Command Prompt"
Command prompt shows list of all actions that were executed (because no @echo off)
Should be "Visual Studio 2010 Command Prompt"
Opening command prompt this way should be nearly silent
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 6/9/2009 at 2:24 PM
Thanks for the report. This has been fixed for Visual Studio 2010 Beta2.
Visual C++ Libraries Development
on 6/5/2009 at 2:25 AM
When using the steps suggested the title is ok.
Steps to reproduce: Windows Button, All Programs -> Microsoft Visual Studio 2010
Inside Visual Studio 2010:
Tools -> Visual Studio 2008 Command Prompt
I will attach a screenshot
on 5/28/2009 at 8:46 PM
We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Visual Studio Product Team
on 5/28/2009 at 8:44 PM
Thanks for reporting this issue. We are unable to reproduce this issue in VS2010 Beta1. Before we go any further, i would like to double confirm with you that you did the following steps to reproduce this issue.
Click Windows Button, All Programs-> Microsoft Visual Studio 2010-> Visual Studio Tools-> Visual Studio 2008 Command Prompt
If possible, could you please take a screenshot of this issue? Thanks for your help and support.
on 5/27/2009 at 2:37 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com/)
to post a workaround.
Please enter a workaround.
© 2014 Microsoft