Visual studio 2015 enterprise debugging multiple solutions

Question

0.00/5 (No votes)

See more:

, +

Hi,
I have two solutions lets say SolutionA and SolutionB. Here SolutionB has class library which is referred in SolutionA. Now I want to step-in through the SolutionB from SolutionA while debugging it.

Please assist.

Many Thanks

What I have tried:

I tried this, sort of working but not completely.
a) opened both solutions in separate VS2015 instances with break points in it.
b) Unchecked "Enable Just my code".
Ran solution A and hit the breakpoint in SolutionA then I did F11 for Step-in to SolutionB. It was stepped-in but respective file (Which is in SolutionB) opened in same VS2015 instance where SolutionA is running.

I want debugger should jump on to SolutionB VS2015 instance.

I tried even attach to process, It was doing same along with SolutionB VS2015 instance went into some weird blocking state (there were four icons on top. Go to live visual tree,Enable selection, Display layout adorners, track focused element)

Posted 28-Mar-18 12:03pm

krishna Dev

Updated 30-Mar-18 9:57am

v5

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Answer 1 · 2018-03-28T21:48:00

Solution 1

You only need a single instance of the debugger to do this. Start debugging the executable project, and when it makes a call to the class library use the "step into" button (or F11), to follow the path through the library code.

Posted 28-Mar-18 21:48pm

Richard MacCutchan

Comments

krishna Dev 30-Mar-18 12:36pm

I did. but debugger not jumping to another solutionB instead it is opening same class file (preview file) with in SolutionA instance. Symbols and dll loaded successfully

Richard MacCutchan 31-Mar-18 3:48am

Of course it won't; you cannot run a DLL in isolation.

Wendelius · Answer 2 · 2018-03-30T09:58:00

Solution 2

As far as I know you can't use two debuggers for the same process.

If solution A is the executable use the debugger on that. Before starting the debug session, open the desired file from Solution B to Visual Studio where Solution A is open. Make sure that you open the solution B file from correct folder, the folder from which the assembly B is compiled that you're referencing.

Place a breakpoint on a desired code line in the newly opened file and start debugging. It now should stop once the breakpoint is hit.

Posted 30-Mar-18 9:58am

Wendelius

Comments

krishna Dev 30-Mar-18 16:57pm

SolutionA is console application and SolutionB is an class library. I compiled SolutionB added its dll & pdb to SolutionA. Openned both solutions separately in different VS2015 instances. But no luck

Wendelius 30-Mar-18 17:03pm

As I said, try using just one Visual Studio instance. Open solution A in it and also open a file from Solution B. Place a breakpoint in that file and run the debugger. There's quite similar conversation here: Stepping into a referenced DLL[^]

krishna Dev 30-Mar-18 17:09pm

Currently Its working like that. SolutionB file opening in solutionA while debugging. I can happily can step through the SolutionB file, but I am looking for debugger should jump to new VS2015 instance where SolutionB opened.
I need this way because there are few more dependencies in SolutionB (like Solution-B dependent on Solution-C)

Wendelius 31-Mar-18 1:40am

As said in the beginning my understanding is that you can use only one debugger for a single process. You cannot switch debugger during the debug session.

If you have pdb's for the other assemblies also you should be able to jump into their code as well. Just make sure that you have referenced all assemblies in assembly A.

Also you can open an interesting file from assenbly C, D, ... beforehand and place breakpoints if needed.