Hi Bill,

I just posted something today that might shed some light on "loader" programs. See Message #1069797.

Also, we've tested our application in the scenario you asked about (running from a network drive) ... it's somewhat related to the above topic. You don't point to a mapped network drive however, you need to specify where the .exe is by using http. The app doesn't actually run on that drive and DLLs are downloaded to the client machine. There's more to it than that, but I don't remember all the specifics right now, other than we use an XML file to specify where the URLs are for grabbing DLLs. I guess I should have paid more attention when the guys were testing it.

If you don't get enough info from the resources that Eric posted, let me know and I'll go ask about it (I'm not in the office today and the guy that knows isn't available today to ask. Maybe tomorrow afternoon).

~~Bonnie




>Ok, thanks. I'll look at them.
>
>Bill
>
>>You can start with these:
>>-http://www.utmag.com/wconnect/wc.dll?LevelExtreme~9,7,10,1286
>>-laucher.zip from http://www.franklins.net/dotnet/
>>
>>
>>>A developer here is trying to deploy a client/server .NET desktop application from the network. They were originally trying to run the application directly from the network and .NET is requiring the client to have full (I think, or at least high) rights to the files on the network which is a security issue. I mentioned that many run a small "loader" exe to download the files onto the client's machine and then spawn a process to run the application. However, I have not done this myself so I have no experience or code. Therefore the questions are:
>>>
>>>1) Is there a best/permissible/proper/etc. way to run a .NET client/server desktop applciation froma a network drive?
>>>
>>>2) What is the proper methodology for a "loader" exe to download the proper files and spawn a process to run the application? Also, is there any available (template) code to accomplish this?
>>>
>>>Thanks,
>>>Bill