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 seems that in this area Solution Explorer is better. For example the context menu doesn't show a Reload Project option when right-clicking on a an unloaded project.
I am working with solutions containing many projects and need to be able to selectively load and unload projects: in manually selcted sets, at solution level, folder level and project level.
It would be nice to have the Navigator be at least on par with the Explorer.
If you run the performance profiler and go to the "Functions" view, you can't bring up the find window. I have tried through the menu and by using Ctrl + F.
The only way I am able to get it to display, is by opening the find and replace dialog first and then changing the drop down to "Quick Find". Has anyeone else seen this bug?
With the last update or two something has happened to Remove and Sort on save that has made it rather frustrating. If you save while there is a syntax issue the result is that this feature will remove all of the using statements.
Hi, I have an "Install Error" like this:
Install Error : System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.BeginInstall(IInstallableExtension installableExtension, Boolean perMachine, AsyncOperation asyncOp)
at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallWorker(IInstallableExtension extension, Boolean perMachine, AsyncOperation asyncOp)
Can anyone help me?
Thanks for reply.
We often copy references to a local lib folder (even if they're in the GAC) so that they can be committed to version control. When I add a reference to an assembly by specifying the local lib path and then try to copy and paste that reference into another project, the same assembly is not always referenced.
When the assembly is in the GAC, it seems that the reference points to that path. Also, I've noticed with NLog (which has several versions) that I don't even get the same assembly version (e.g. I start out with the version for .NET 2.0, but the pasted reference points to the .NET 4 version).