John,
The reason for this is that .NET doesn't fully trust assemblies that are
located on another machine. In order to get around this, you will have to
go to the .NET framework configuration tool and set up the assemblies so
that they are given the appropriate rights. You will have to strong-name
the assemblies, so that you can identify them in the configuration tool.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- nick(dot)paldino=at=exisconsulting<dot>com
"john bailo" <jb****@vestcom.com> wrote in message
news:fa******************************@news.teranew s.com...
I wrote a c# program that does some file manipulation on
a remote server. Testing it from my workstation, it ran
fine.
When I copied it to another server, and ran it from
there, on load, it threw a balloon message:
"This application is running in a partially
trusted context. Some functionality in
the application may be disabled due to
security restrictions."
What is the answer to this?
