Hello!

I have a solution that create a class library dll.
I have also a solution where the main is located so this solution create a
exe file.

Now to my question if I want to debug the dll do I then have to add the dll
project to the solution where the main is located.

//Tony

On 9/1/2011 7:17 AM, tony.johansson wrote:
> I have a solution that create a class library dll.
> I have also a solution where the main is located so this solution create
> a exe file.
>
> Now to my question if I want to debug the dll do I then have to add the
> dll project to the solution where the main is located.

Other will have to answer the question you asked.

I will just point out that I would choose another
strategy:
* write extensive unit tests for the class library to
find most of the bugs before another project
consumes it
* if necessary to track down the bug use the debugger
in the class library project
* modify the class library to use a logging framework
like log4net (or NLog or Enterprise Library or whatever
you prefer) to be able to trace what is going on inside
the class library

Arne

On 1 Sep., 13:17, "tony.johansson" <tony.johans...@systeam.se> wrote:
> Hello!
>
> I have a solution that create a class library dll.
> I have also a solution where the main is located so this solution create a
> exe file.
>
> Now to my question if I want to debug the dll do I then have to add the dll
> project to the solution where the main is located.
>
> //Tony

Hello Tony,

If I well understood your question, you wrote a dll, referenced it in
an exe project,
and your goal is to debug your dll when you run your exe application.
You have two ways to do it :
- As you said, you can add the dll to your exe solution and
referenced the dll project
from your exe application
- You can also open the dll project, run your application, and
attach the application process
to your dll ==> Go to debug menu, choose attach to process, and in the
list choose the application
process