S
Saira
Hi all
I have had an add-in that has references to several assemblies running
smoothly for some time. recently i have lost the ability to debug it.
When the solution starts, the symbols do not load.
I narrowed down the problem to a timestamp mismatch between the pdb files
and the dlls.
When Excel loads, it loads the .net assemblies from the GAC, however these
are not the current dlls that I am debugging with (these are in my bin
directory). as a result the pdb file (in the bin director) does not match
the dll being loaded into memory.
If I do a build and then copy all the dlls into the GAC immediately and then
run the app, all symbols load immediately and i can debug properly.
Does anyone know how I can work around this, e.g. by forcing the bin
directory dlls to load, rather than those in the GAC. It seems that because
this is an add-in I am unable to control this behaviour.
TIA
Saira
I have had an add-in that has references to several assemblies running
smoothly for some time. recently i have lost the ability to debug it.
When the solution starts, the symbols do not load.
I narrowed down the problem to a timestamp mismatch between the pdb files
and the dlls.
When Excel loads, it loads the .net assemblies from the GAC, however these
are not the current dlls that I am debugging with (these are in my bin
directory). as a result the pdb file (in the bin director) does not match
the dll being loaded into memory.
If I do a build and then copy all the dlls into the GAC immediately and then
run the app, all symbols load immediately and i can debug properly.
Does anyone know how I can work around this, e.g. by forcing the bin
directory dlls to load, rather than those in the GAC. It seems that because
this is an add-in I am unable to control this behaviour.
TIA
Saira