VSCommands 3.3.0.0 Released
New version of plugin is available from Visual Studio Gallery so download it now!
New in this release:
Apply Fix
You can now automatically fix several build errors and warnings.
Take the well know ‘file being used by another process’ error as an example:
Unable to copy file xxx to yyy. The process cannot access the file xxx because it is being used by another process.
With VSCommands you can now right click on error message, select Apply Fix command
and click Ok to end all processes that are currently using this file:
Another example of frequent problem that can be now easily solved is key import error:
Cannot import the following key file : xxx.pfx. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: VS_KEY_XXXXXX
Now when you click Apply Fix the certificate will be installed to the correct CSP.
More details about all supported errors and warnings will be coming soon.
Open Powershell
Since old Open Command Prompt is going out of fashion, VSCommands now supports
Open Powershell command which will open a new Powershell window and load Visual Studio environment variables for easy access to all VS tools.
Note that to use it properly you will have to first update the Execution Policy
by executing Set-ExecutionPolicy Unrestricted command.
Open Command Prompt
Open Command Prompt will now execute with elevated privileges.
Related posts:
