Is there a way to navigate between two Visual Studio Solutions?
For instance, I have two solutions: One with a various utility code and one comprising my actual app. When I hit F12 in the app solution, I am taken to a 'metadata' file, with function definitions only. Ideally, I would like to taken to the file in another instance of Visual Studio with the utility solution open.
Currently, I copy the thing I am seeking a definition on, then switch to the other instance of visual studio and conduct a search. Just curious if there's a faster way of doing this.
Not as far as I know. The only workaround that I know is to add the "utility" project(s) to your app solution. If you don't change them much VS won't try to recompile them all the time, and you'll have access to the code.
Using ReSharper and presumably a combination of the debug PDBs (generated with your Utility class build) then you're able to get right into the source of your libraries using F12 without needing to go to the other instance.
Related
At this new company I joined there is a very big and huge multi solution product that I'm working on.
So sometimes when I'm looking through the source i have an interface that has an implementation that is within a project in another solution and when I Ctrl-F12 click that interface I get a "The symbol has no implementations." dialog box from Visual Studio, because it can't find the piece of code where the interface is implemented in.
Is there any way of like telling Visual Studio to just look in some specific directory for the code it's looking for without having to put everything into one giant huge solution that makes Visual Studio explode? I tried that btw and Visual Studio exploded.
While debugging the software there's no problem with the navigation because the debug symbols contain the paths to the source and stuff (if I remember that correctly).
I'm also using Resharper so if there's anything that Resharper can do to help there I wouldn't mind either.
Does anyone know about a plugin (or built-in) functionality for quickly switching Visual Studio Solutions?
I'm working in a multi-solution project and need to switch the solution quite often (by reusing one of the open Visual Studio instances)
Any ideas?
If not, how hard would it be to write a plugin on my own?
You can add solutions to favorite links with my Favorite Documents extension.
Is it possible to load more than one solution in the Visual Studio .NET IDE at once, so that both solutions appear in the Solution Explorer ?
Thanks
No, Visual Studio can only load one solution at a time. There's a Microsoft Connect suggestion on this very topic.
What you can do, though, (aside from an obvious option of opening several instances of Visual Studio) is to "Add Existing" project to either solution, or create an ubersolution which will include them both.
You can "add existing" picking .sln file type to current solution
or you can try to automate the process you can try playing around with this tool (might make sense if you have to do it repeatedly):
http://code.google.com/p/merge-solutions/
Is there a way to tell Visual Studio 2005 to just ignore source control binding when opening a solution? I sometimes need to load a solution for which I don't have access to the source control server, but Visual Studio insists on trying to connect anyway, meaning I have to click "temporarily work offline in disconnected mode" for every project in the solution (of which there are about 20) as it loads. For some reason, it also tries to check each project out immediately after I've told it to work offline, so I have to click past that dialog box too.
As I will never need to edit anything in this solution, is there any way I can open it and have Visual Studio just ignore the fact it has source control bindings in it?
Edit: Ideally, I'd like a way to do this without having to change the project/solution files. They change fairly frequently, so I'd have to redo any changes every time there was a new version (otherwise I'd just unbind them once and it wouldn't be a problem).
Thanks for the replies so far.
The source control bindings are stored in Visual Studio solution file (.sln). For TFS for example, it contains a global section for TFS information and the solution projects added to TFS. You can edit the solution file to remove these bindings manually. I would suggest making a copy of the solution file first. However, I would recommend removing bindins via Visual Studio. Open your solution and go through the offline scenario. Then go to File/Source Control/Change Source Control (VS 2008) to bring up the UI that shows you the source control bindings in your solution. There you can manage the bindings including unbinding them. Once unbound, the next time you open the solution, VS should not have a need to access the source control.
I've been looking for a way to disable Integration between SourceSafe 2005 and Visual Studio 2008. We are forced to use SourceSafe being in a corporate environment and all. SourceSafe is fine on its own if you treat it like a baby. As soon as you try to do anything approaching useful it starts to break. God forbid you try to use the integration with Visual Studio. Being that I didn't want the "Bindings removed" so that it doesn't confuse other devs on the team I needed to be able to tell Studio to ignore the solution and project bindings and continue on it's merry way.
I followed the registry hack suggested in the following post
Removing SourceSafe Integration from Visual Studio 6
Studio did what I wanted...sort of. It removed the SourceSafe integration. However when I opened up a source controlled solution it asked me if I wanted to remove the bindings.
"the projects will be treated as not under source control"
No I don't want you to remove the bindings from the files, I want you to IGNORE them. This dialog pops up every time you open the solution/project file and there is no way around it.
My solution at the moment seems to have worked...for now.
File->Source Control->Change Source Control...->Disconnect
I hope this helps anyone else in the position of having to use SourceSafe but can't remove the bindings from the files themselves. WHY, Microsoft, WHY would you put the bindings in the files themselves?
/rant
I am using a solution with many projects in Visual Studio 2005. Unfortunately we are using the testing tools. My problem is that a lot of the time when I open up Test Manager by double clicking on my VSMDI file to do some testing, I get the hourglass for at least 10 minutes while Microsoft's horrible code does god-knows-what, I guess trying to find new tests? Does anyone have a workaround for this?
Thanks!
I know this is now an old question, but I've got used to using MSTEST now. Here's my recommendations for effective use in a large solution:
Use the shortcuts CTRL-R, T (or CTRL-T for debug) to run the tests in the current context (i.e. namespace, class, method). This fits reasonably well with a TDD approach.
Don't use Test View, Test Lists or Test Runs windows if you can avoid it.
Generally I find I only get problems with the VSMDI file when switching between different build configuration. VS thinks for a while then prompts me to check out the VSMDI file (and I just cancel the check-out dialog).