D
David
I have an ASP.NET application that accesses an out-of-process COM server
that is single-threaded (STA). All of the resources that are available on
the machine, such as network shares, are accessible and work correctly in
the COM server if the ASP.NET application is run from within Visual Studio.
As soon as we are not running in Visual Studio, it is no longer able to
access the network shares. Yet, other COM based applications on the machine
can use the COM server with the COM server being able to access the network
shares correctly.
Also, it is not able to access the network shares even if the COM server is
launched with an administrator account on the machine.
I am certain that the problem is some security setting(s), however, I am not
sure what the difference is.
Can anyone point me in the right direction?
Thanks,
David
that is single-threaded (STA). All of the resources that are available on
the machine, such as network shares, are accessible and work correctly in
the COM server if the ASP.NET application is run from within Visual Studio.
As soon as we are not running in Visual Studio, it is no longer able to
access the network shares. Yet, other COM based applications on the machine
can use the COM server with the COM server being able to access the network
shares correctly.
Also, it is not able to access the network shares even if the COM server is
launched with an administrator account on the machine.
I am certain that the problem is some security setting(s), however, I am not
sure what the difference is.
Can anyone point me in the right direction?
Thanks,
David