Debug Shared Assemblies

  • Thread starter Thread starter Rakesh
  • Start date Start date
R

Rakesh

Hi All,

I have a created a solution in VS.NET, which has several
projects.

The output of 2 Class Library projects, is deployed in the
GAC. The reference of these assemblies is added in the
other projects using the File References, so the CopyLocal
property of these references are false.

Now when I try to debug the solution, I am not able to
debug the code in shared assemblies. The debugger does not
go inside that.

Help needed urgently.

Thanks
Rakesh
 
If you compiled this projects after you have put them in the GAC you must
make sure to put them in the GAC prior to starting the debug session.

If, for example, you put them in the GAC and changed some code in one of the
assemblies, the GAC version does not match the version compiled and VS.NET
won't go into debugging.

Eran
 
Rakesh said:
Hi All,

I have a created a solution in VS.NET, which has several
projects.

The output of 2 Class Library projects, is deployed in the
GAC. The reference of these assemblies is added in the
other projects using the File References, so the CopyLocal
property of these references are false.

Now when I try to debug the solution, I am not able to
debug the code in shared assemblies. The debugger does not
go inside that.
Click to expand...

Make sure that the PDB files for the assemblies that are in the GAC are
also in the same folder that DLLs are in. in other words, the PDB files
must be in the GAC with the DLLs.
 
I tried that, but still I am not able to debug into shared
assemblies.

I am using the file References for the shared assemblies
in my project and not the Project references.

Is that the reason??

Thanks and Regards,
Rakesh
 
One option is to use the project references. If not at least make sure that
you put the assembly and the shared assmebly in the same solution when you
debug.

I hope that will help a little bit.

In addition to that I want to make sure this is not a versioning problem,
therefore I need to know if you are using signed assemblies and are you
chaning their version number (do you have a "*" in the version in the
assembly info?).
If so, each build you have a different version number and if you are putting
them in the GAC, that might trigger an unwanted effect of running with a
certain version and debugging with another.

Eran
 
Thanks Eran,

I will give it a try with using Project References.

Version number is not the issue, i'm using 1.0.0.0 in the
AssemblyInfo.

Regards,
Rakesh
 
Back
Top