Our Blog

Ok, with todays’ development efforts I am in need of a quick way to open a command prompt to the location of the solution.  Here is a quick tip on how to enable a keystroke to immediately open one for you (while working within vs.net).

Tools > External Tools “Add”

image

Use the following values

Title:    VS Command Prompt
Command:    C:\Windows\System32\cmd.exe
Arguments:    /k “C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\VsDevCmd.bat”
Initial Directory:    $(SolutionDir)   (You can also use $(ProjectDir) to open command prompt in the location of the current project … i like this better)

After you hit OK VS Command Prompt command is available under Tools

image

Now you can add a Key Stroke command for this…

Tools > Options > Keyboard (here i have added Alt-C).  Shown below the only thing to remember is this was my 2nd external tool so I had to look for Tools.ExternalCommand2 to attach my keystroke command.

SNAGHTML58a67cb2

Now Smile I can click Alt-C and immediately a command prompt window opens to the my solution directory. 

Error: Could not install …
Error: Value cannot be null.
Parameter name: key
Usage: new [options]

When building a new solution template for ASP.NET Core solution, I received the above error.  I had not seen this with prior template build efforts.  This was new with .NET Core.

The error occurs when one of the node_modules folders contain a template.json file.  The solution for me, was to entirely remove the node_modules directory before attempting to build the template.

Reference: https://github.com/dotnet/cli/issues/8989

About Us

Web/Mobile Solutions

Our Contacts

Cincinnati, OH 45069