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

Barry McDonald
7/13/2004 3:36:03 PM

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

Ed Kaim [MSFT]
7/13/2004 5:32:17 PM

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/cpconIntroductionToIsolatedStorage.asp).

[quoted text, click to view]

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