Debugging .net libraries in both the GAC and local folder
- From: "phnimx" <phnimx@xxxxxxxxxxxxx>
- Date: Fri, 8 Dec 2006 14:45:05 -0500
Hi ,
We have developed a number of plug-in .NET Library Components that we
typically deploy with our various applications by installing them into the
GAC.
Each of the applications contains an app.config file referencing arbitrary
versions of the plug-in components they wish to consume.
Here's the problem:
Assuming I have installed any one of our application software,
when working on any of these plug-in library assemblies as a developer in
Visual Studio, I'd like to be able to debug the plug-in library assemblies
similar to the way we can in C++, either select a surrogate exe that
references the plug-in, from the VS Project/Debug tab to use for debugging
or "Attach to Process".
Neither technique works. I can't set or hit any breakpoints I've set. What's
worse, I can't use the VS Disassembly Window to reference the disassembled
code and set a breakpoint there either, as it never finds the symbols.
My questions:
1 Can anyone supply a tip on how to truly debug a local library assembly
(dll) when the same version of that assembly resides in the GAC.
2 Is there a technique for debugging the library assembly (dll) that resides
in the GAC?
3 Do assemblies have the concept of symbols and symbol files?
4 Can anyone supply web links to advanced debugging techniques in .NET,
specifically for C#?
Thanks
.
- Follow-Ups:
- RE: Debugging .net libraries in both the GAC and local folder
- From: "Jeffrey Tan[MSFT]"
- Re: Debugging .net libraries in both the GAC and local folder
- From: Michael Nemtsev
- RE: Debugging .net libraries in both the GAC and local folder
- Prev by Date: Re: Auto-updating GAC; loading from GAC vs. server
- Next by Date: Re: Why use "Public" with exe projects?
- Previous by thread: [News] Developers Embrace Java, Drop Visual Basic
- Next by thread: Re: Debugging .net libraries in both the GAC and local folder
- Index(es):
Relevant Pages
|