Question: Is it possible to centralize the DLL location
when using .Net COM+ components? We have three servers
that currently utilize the same DLL set on each machine.
I'd like to centralize this onto a single machine. Each
server would then map to this directory remotely. I've
tried this but it kicks of a slew of .Net
System.Security .SecurityExcept ion: errors when I attempt
to register this object into W2K 'Component Services'. If
I refer to a local directory the same DLL set registers
fine. Any recommendations here? Thanks
when using .Net COM+ components? We have three servers
that currently utilize the same DLL set on each machine.
I'd like to centralize this onto a single machine. Each
server would then map to this directory remotely. I've
tried this but it kicks of a slew of .Net
System.Security .SecurityExcept ion: errors when I attempt
to register this object into W2K 'Component Services'. If
I refer to a local directory the same DLL set registers
fine. Any recommendations here? Thanks