Hi, I have a .NET DLL that runs in a COM+ application on a W2K server.
I have no trouble calling this DLL until I change a parameter for a
class instead of a base .NET type. Then i receive the "Cannot find
assembly xxx" error.
If I put this assembly in the GAC it works but then I lose all debug
information (doesn't seem to fin the .pdb file)
Does anyone have an idea how to solve this ?
thanx
I am able to debug objects in the GAC if I use the command-line gacutil,
like so:
gacutil /nologo /i C:\Path\To\Project\obj\Debug\Project.dll
[the .pdb file resides in the same directory,
C:\Path\To\Project\obj\Debug\ ]
Does that help with your debugging problem?
As far as your problems changing parameters, you should stop the COM+
application before recompiling your object, so COM+ does not keep a hold of
the prior version of your DLL in memory. In Control Panel, go to
Administrative Tools and run Component Services, then open up Component
Services, Computers, My Computer, COM+ Applications, right-click your
application and select Shut Down. Make sure the ball stops spinning, and
then recompile your DLL. (If that doesn't work, you could try deleting the
COM+ application altogether, recompile, and re-register the component[s] in
COM+.)
> Hi, I have a .NET DLL that runs in a COM+ application on a W2K server.
>
[quoted text clipped - 8 lines]
>
> thanx
Alex - 30 Mar 2004 17:01 GMT
Thanx for you response.
I'm not trying to debug the COM+ application, instead I try to log to a
file the trace information of an exception. Thats where I need to know
the exact line number of the error. But whenever I place my dll in the
GAC that information disapear as if the GAC doesn't know where the pdb
file is.
thanx