Hello,

I have a .NET executable and I'm trying to put it on a server. I'm getting a security error, and the executable won't run. I put the whole project out on the share and open it, and I get the message:

The project location is not fully trusted by the .NET runtime. This is usually because it is a network share or mapped to a network share not on the local machine. If the output path is under the project location, your code will not execute as fully trusted and you may receive unexpected security exceptions.

I can understand why the project then wouldn't work, but how do I get the executable to work?

Thanks,

Brian Mains

__________________
Brian

I assume you are attempting no touch deployment through IIS.

The .NET runtime installs some extra functions on the client under administrative tools in control panel. You need to set security in there to give your application full trust for the server you are deploying it from. You could build this into your install package.

You may also want to get hold of a little program called Netrun which will launch your app without throwing up a browser window and it also overcomes the issue that IIS doesn't like serving app.config files.
(I found this out from "Fast track VB .NET")

This executable actually is being used by a DTS package, but I have several options of placement for the executable. Should I put it on a web server?

Also, this executable uses Trace.WriteLine() to output statistics. Should I disable this? Is that causing the problem?

ignore my previous comment about no touch deployment using IIS.

If the exe lives on the same machine that is running the DTS package you should not have any problems. If you want to put it on a network drive you will need to configure .NET security on the machine running the DTS package to trust anything comming from that network drive.

Would this be established through the .NET Framework 1.1 Configuration tool in the Administrative tools panel within the Control Panels?

Yes, you can use the wizard to 'trust an assembly' and this will create an entry under 'Runtime Security Policy->Machine->Code Groups->All_Code'. It's been a while since I did this but I'm sure you can also export the setting as an install package once youv'e got it working.

Same problem here, but all the wizards I try to run lack an interface. I see the description on top, and the next/previous buttons below, but nothing else. <sigh>