Hi!
Define very restrictive security for it, so it would not run until you return security settings back :-)
HTH.
>When I update a COM+ DLL, I go into Component Services and stop the component. If before I can copy the new DLL, an ASP.NET hit comes in and the DLL is loaded into memory again, the copy will fail.
>
>How can I prevent the COM+ component from being reloaded into memory until I explicitly start it?
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.
