Deploying/Executing C#.Net .dll in a client/server environment

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Barry McDonald - 13 Jul 2004 23:36 GMT

I have C# .dll that I created and applied to the same directory as the app .exe. In my code I use the streamreader functionality. I have the app and .dll installed local to my system and all runs correctly. I take the application and place on a drive located on the network. The application can access the .dll however streamreader errors out. Seems as though the file path (eg. c:\temp) that I pass to the streamreader while installed locally is able to be resolved. However once the logic is called over the network the file path cannot be resolved. Is there something I am missing here?

Thanks,
Barry

Reply to this Message

Ed Kaim [MSFT] - 14 Jul 2004 01:32 GMT

This may be due to security restrictions. When you load a DLL from a remote
source, it's loaded with restricted permissions. You can either elevate its
permissions using the .NET Framework Security config wizard (in
Administrative Tools off the Start menu) or use IsolatedStorage
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cp
conIntroductionToIsolatedStorage.asp).

>I have C# .dll that I created and applied to the same directory as the app
>.exe. In my code I use the streamreader functionality. I have the app and
[quoted text clipped - 8 lines]
> Thanks,
> Barry

Reply to this Message

Deploying/Executing C#.Net .dll in a client/server environment

Free Magazines