Great tools, when they work. There are bugs, especially with Copy/Paste References, which doesn't work at all (E_FAIL), and it appears no there has been no work on the project for 2.5 years. Release the source to the community so we can update it and fix bugs.
It isa failure to assume that all users us CMD.EXE as command prompt.
The PowerCommands should use the COMSPEC environment variable to get the current selected Command Line executor!
I personally use 4NT/TCC (from JPSoft) over years!
I would like to be able to collapse all as opposed to just collapse projects. For example, Solution Folders do not get collapsed when you select Collapse Projects. I was able to modify the 2008 version of the Power Commands to accomplish this because the source code was available. Any chance the source code will be published soon for the 2010 version?
An additional command that would be nice is an "Open in ILDasm" command when you click on a dll. I help with a .Net class and often times we want to show the IL to make a point - and this command would make it so easy.
I added something similiar to my PowerCommands project for Reflector (http://powercommands.codeplex.com/) - but I would love to have it in Visual Studio instead.
It'd be nice to have this feature trigger every time the file is saved, not only on the save command is invoked.
The files are saved when building, for example, but they're not formatted by the extension.
Is it possible to cange the command "Remove and Sort Usings on save" into two commands: "Remove Usings on save" and "Sort Usings on save"?
Its getting really bad when the code is saved in release state and then uploaded. Someone else checks out and tries to build in debug state and he is missing all the Usings for the additional code. so i don't want to remove the Usings, but sort them to match the StyleCop settings.
Would be great!
I second this, definitely. I'd also like a "Remove usings on close" feature as I'm finding I'm adding a new class and losing the default usings (which I plan to use) very quickly as I first hit save after just a couple of lines and then have to put them back in manually as I go.
VS2008 PowerCommands download was an msi that could be installed on any machine. Why no msi with VS2010?
I'm trying to work out what to do with the PowerCommands.vsix folder that i've downloaded to enable the ExtensionManager to pick it up.
Any ideas welcome...
the unused usings removal is really great feature, however, during working with VS it gets sometimes quite annoying. It removes them too soon, and it does so also when you do some refactoring task (like renaming a class) when you did not save the file. Since refactoring is not limited to a valid code file, plenty of namespaces gets removed in case the syntax errors lead to unparsed files.
I think it would be a bit more useful if it removed the using on build instead of on file save (or eventually even on release build only). This would also fix removing the namespaces after refactoring.