Comments
4 comments
-
Good point. Perhaps CAS is preventing the application from inheriting the COR_PROFILER environment variable the Profiler needs to set in order to get the code from the CLR for the COM+ app.
-
I will disable the CAS in the DLL and give it a try this evening and let everyone know what I find out.
-
The problem was not to do with the CAS but the identity under which I had the com+ service running, it was set to use the 'NETWORK SERVICE' account and I changed it to 'INTERACTIVE USER' for testing purposes
-
Hi Ollie,
Good call! I'd have thought it would work better the other way around though...
Add comment
Please sign in to leave a comment.
The COM+ component is a service component and is a debug build version, the PDB is with the dll - I am testing from a C# console test harness.
The only thing I could think it might be is the code access security that is applied to class and interface methods in the COM+ component. Would CAS prevent the profiler from working correctly?