Re: Run app from network share

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi!

For this, and to run applications in the security zone of network shares, we're signing our .NET assemblies with a strong key that is shared by all products from our company. We're then using a batch file (this can also be done in a UI, but more cumbersome for automated installs) to tell .NET to grant software signed with our key more access rights. I think that's a pretty "clean" way of doing it, with not having to disable or change any more global security settings, but just add some trust for the apps we're developing. They key we're signing our assemblies basically works as our signature or identity.

See more here:
- Signing an assembly in Visual Studio: http://msdn2.microsoft.com/en-us/library/ms247123.aspx (you'll only need to do this once per application)
- Running a .NET application on a server: http://weblogs.sqlteam.com/jhermiz/archive/2007/08/14/60284.aspx

/ Jonas

"B" <zelenooki05@xxxxxxxxx> wrote in message news:fjkecs$os7$1@xxxxxxxxxxxxxxxxxx
Can somedoby tell me the steps, or perhaps examples, which I have to
complete to access .net application on client computer from network shared
folder on server computer??

I made a release of my appplication and it is on my D disk (D:\Test) and I
use third party control (xyz.dll) which is
in the same folder like exe file.

So, please.....

These are the steps on server:
1.
2.
...

These are the steps on client:
1.
2.
...


When I remove xzy.dll from my application, everything works fine. I can
start the application from network folder just through the shortcut
on client computer. But when I drag xzy.dll from toolbox and tried to start,
it shows me this error: "An error occurred creating the form. See
Exception.InnerException for details. The error is: Request for the
permission of type 'System.Security.Permissions.FileIOPermission, mscorlib,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed."

Please help me.
Thanks!

.

Relevant Pages

  • Re: Read Only Error Message & Crashes
    ... I've had a similar problem, although I did not crash, but did play the ... whack-a-mole game. ... > part (stored on our network) into an assembly hit save and it crashes. ... > parts or sub assemblies in it and you go to measure or mate one of ...
    (comp.cad.solidworks)
  • Re: Hosting from a network share.
    ... >Subject: Re: Hosting from a network share. ... >group to include the assemblies on your network share, ... >(and grant permissions to) your .dll assembly using the ... just to help poor old IIS out. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Sharing Code
    ... But this is a red-herring you've thrown in and really has nothing to do with the general precept and good practice of signing any assembly you create because it is *the easiest thing to do* when creating the most flexible of assemblies. ... How are you making it sound oh so time consuming to add a reference to a key file when you know damn well it takes seconds, which in any normal developer's book is zero-effort. ... in order to avoid warnings I moved the signing from AssemblyInfo to the properties pane. ...
    (microsoft.public.dotnet.languages.csharp)
  • Read Only Error Message & Crashes
    ... part (stored on our network) into an assembly hit save and it crashes. ... This has happened in several different assemblies and with lots of ... we control permissions by storing files in different folders (a working ... directory and a controlled directory). ...
    (comp.cad.solidworks)
  • RE: Calling a Dot Net DLL from MS Access
    ... Still publish the assembly in the network share, ... all the assemblies in intranet shares (not ... Here are the basic steps to create such a setup project: ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.framework.interop)