You need to put the .pdb file in the same physical directory as the assembly in the GAC. Do do this you have to use the command line as a shell extension masks the physical makeup of the GAC. You want to put the .pdb file in the following directory:
c:\<windir>\assemblies\gac\<simple name>\<version>_<culture or blank>_<public key token>
You dont' want to do that - debug it when it's in debug mode and in the
application or debug directory or whatever. Then when you know it works as
you want, put it in release mode, do a build, build the setup project, and
that will install it into the GAC. You shouldn't ever need to *debug* it once
it's already in the GAC...
If you 're doing production-mode debugging (i.e. debugging that *has* to be
done on a computer that doesn't have the IDE installed) you'd want to be
doing a "special edition" build with a setup project that doesn't install to
the GAC.
You dont' want to do that - debug it when it's in debug mode and in the
application or debug directory or whatever. Then when you know it works as
you want, put it in release mode, do a build, build the setup project, and
that will install it into the GAC. You shouldn't ever need to *debug* it once
it's already in the GAC...
If you 're doing production-mode debugging (i.e. debugging that *has* to be
done on a computer that doesn't have the IDE installed) you'd want to be
doing a "special edition" build with a setup project that doesn't install to
the GAC.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
