Running .exe via a mapped drive

[SteveShanks]

Hi all

Am I able to install my app .exe on a sever along with the database etc and then run this .exe on a mapped via a shortcut to it from the client workstation instead of installing the .exe on every workstation?

Where do I need to install all the DLL's etc?

Many Thanks
Steve

 

[ca8msm]

The actual executable file can be executed from the server by the client, but if there are any specific DLL's that need to be registered, they will still need to be registered on the client's machine.


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[SteveShanks]

Thanks although it is still not working.

Even if I do a standard install on the server machine to a directory on the c:\ drive, the app runs fine, however, if I try and run the app from the same machine with the mapped drive in place and run it via the mapped drive I get an error from the app when it tries to access the IO stuff

"Request for the permission of type System.Security.Permissions.FileIOPermission, mscorlib, etc etc"

Any thoughts?

Thanks
Steve

 

[ca8msm]

It seems as though executing code from a mapped drive means that it doesn't run in a space that .NET "trusts". This may give you more info:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_prog_rdl_0so6.asp

____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[SteveShanks]

Thanks

This looks like it could be a bit of a nightmare!

Steve

 

[edderic]

Set de server machine for intranet (netwerk) tot FullTrust.

Framwork 2.0 config



Eric De Decker
Visit The Belgium "Visual Basic Group" at

http://www.vbgroup.org

 

[ThatRickGuy]

This has been covered here a few times here, but I can't find my old posts. Its not too bad if you only have to deal with a few machines. But it would quickly become a headache for more.

Goto control panel -> Admin Tools -> .Net Wizards -> Trusted Assemblies

Follow the wizard and give your assemblies out on the network full trust. You don't have to trust any of the framework libraries, but if you make your own .DLL file and reference it from a .Exe file, you'll have to trust both of them.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[SteveShanks]

Thanks

I have looked into this a bit and decided to keep the .exe on each client workstation and just have the data accessed via the mapped drive.

The application is going to be installed by numerous customers straight off the CD so needs to be as basic as possible.

Thanks again everyone

Cheers
Steve