Click here to Skip to main content
Click here to Skip to main content

.NET Command Prompt Here

By , 22 Aug 2003
Rate this:
Please Sign up or sign in to vote.

<!------------------------------- STEP 3 ---------------------------> <!-- Add the article text. Please use simple formatting (

,

etc) -->

Introduction

I find the Open Command Window Here utility in the XP Power Toys bundle absolutely indispensable. Put simply, it adds an item to Windows Explorer's context menu that opens a DOS session in the current directory. This article contains and explains two simple registry hacks that add a .NET Command Prompt Here menu item to Windows Explorer's context menu that runs vsvars32.bat and then opens a DOS session in the current directory. I use this in place of the Visual Studio .NET 2003 Command Prompt shortcut installed by VS.NET 2003. It's not magic. Just simple and useful.

Using the code

Unzip dotNET_cmd_here.zip. Double click on both .reg files contained therein, which should be named  .NET Command Prompt Here - Directory.reg and .NET Command Prompt Here - Drive.reg. This adds the .NET Command Prompt Here menu item that is both described and shown above. When you select the menu item, you get something like the DOS session shown below.

Now you can gacutil and ngen to your heart's content.

Points of Interest

Each .reg script has been tested on several XP Pro systems with VS .NET 2003. The command actually added to the registry reads cmd /k "%VS71COMNTOOLS%vsvars32.bat" , which uses the VS71COMNTOOLS variable added to the environment variables by VS.NET 2003. I'm not sure whether VS.NET 2002 adds this variable so, if you're still using VS.NET 2002, look at your environment variables and add the appropriate variable or <kludge>hardcode the path</kludge>.

If you actually look into the .reg scripts, you'll see that the command is written in hex(2). This has to do with the fact that the value is REG_EXPAND_SZ types rather than the default REG_SZ . If you're a registry maven, this is all old hat. For me, however, this was all new. Thus ends my first CodeProject article.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here

About the Author

flipdoubt
Web Developer
United States United States
No Biography provided

Comments and Discussions

 
GeneralFor VC6.0 PinmemberMG Man11-Dec-06 19:28 
Replacing "cmd /k ..." to
'cmd /k "C:\Program Files\Microsoft Visual Studio\VC98\Bin\VCVARS32.BAT"'
worked for me.
Generaluninstall method [modified] PinmemberMG Man11-Dec-06 18:29 
GeneralRe: uninstall method Pinmemberflipdoubt12-Dec-06 3:05 
Generalwhidbey version Pinmemberandy_p3-May-05 4:44 
GeneralRe: whidbey version Pinmemberflipdoubt27-Jun-05 2:24 
QuestionRe: whidbey version Pinmemberengfelt27-Mar-06 2:46 
AnswerRe: whidbey version Pinmemberandy_p27-Mar-06 3:40 
GeneralNice one Pinmemberdbvaughan29-Mar-05 14:14 
GeneralNice and 2002 .. Pinmemberhotind12-Nov-03 20:34 
GeneralGood Stuff Pinmemberfbougadou28-Aug-03 5:16 
GeneralGood stuff PinmemberTim Stubbs26-Aug-03 22:33 
QuestionDOS? PinsussAnonymous24-Aug-03 5:54 
AnswerRe: DOS? Pinmemberflipdoubt24-Aug-03 6:05 
AnswerRe: DOS? PinsussAnoner25-Aug-03 6:08 
GeneralNice and useful :-) PineditorNishant S22-Aug-03 19:44 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Mobile
Web01 | 2.8.140415.2 | Last Updated 23 Aug 2003
Article Copyright 2003 by flipdoubt
Everything else Copyright © CodeProject, 1999-2014
Terms of Use
Layout: fixed | fluid