Problem Finding Source while Debugging an ILMerged Assembly

We're using Visual Studio 2005 Team Suite. I've got SP1 installed.
I'm currently working with two solutions. Both solutions are built
using the debug configuration.

Solution A contains multiple projects that are built and then combined
into one assembly using ilmerge. The ilmerge operation creates the
pdb for the merged assembly.

Solution B contains multiple projects that have file references
pointing to the ilmerged Solution A assembly. Solution B does not
reference any of the original assemblies / projects from Solution A.

I'm working with both solutions, so I have all the source code
contained in both solutions on my workstation. The source for
Solution A is in a different directory structure than the source for
Solution B.

I'm trying to debug a unit test that's contained in Solution B. I can
step through the code contained in Solution B without trouble. When I
need to step into code that's contained in the ilmerged Solution A
assembly, I cannot get the code to display. I've confirmed that the
symbols are loaded for the ilmerged Solution A assembly, and I can use
break at function to put a break point at code in the ilmerged
Solution A assembly. However, when the break point is hit, I can only
see the disassembly. I cannot get the source code to display.

I've gone to the solution properties - common properties - debug
source files dialog and I've added the root source directory for
Solution A and I've tried adding the project directories for the
different projects in solution A. No matter what I try, I can't get
the source code for projects in Solution A to display while debugging
Solution B.

Has anyone out there gotten this working? I appreciate any help I can
get.

Thanks,
Rob

.

Relevant Pages

  • Re: Not stepping into library assembly
    ... Everything is being built under debug, and all the pdb files are ... *step into* other assemblies that are part ...
    (microsoft.public.dotnet.languages.csharp)
  • RE: Assembly reported as built without debug info - that is not true
    ... enabled or without debug information:..." ... successfully remote debug any other assembly which is not in the GAC? ... in the Modules window's loading assemblies' list, ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.framework)
  • Unable to debug .NET assemblies loaded by a native application
    ... I am unable to debug .NET assemblies loaded by a native application ... Ordinarily one could also debug by attaching to the application's ... The application shows up in the "Attach to external process" ...
    (microsoft.public.vsnet.debugging)
  • Re: CreateProcess Hook
    ... Assemblies are installed into the ... Force fusion to load a Debug - Version. ... key token)) is already installed into the GAC? ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Some interop Questions - C# to unmanaged DLL
    ... by the CLR loader. ... measure i added the debug directory to the windows PATH env. ... it is recommended that the LoadFrom context be avoided. ... | done by installing assemblies in the Global Assembly Cache or in the ...
    (microsoft.public.dotnet.languages.csharp)
Loading