Run only .Net exe

  • Thread starter Thread starter Henk
  • Start date Start date
H

Henk

Is there a way to tell the Scheduler only to run a .NET exe?
What I want is that when someone replaces the file with an ordinary exe, the
scheduler refuses to run it.

How can I do that?

And what are the security risks running a third-party .NET exe with default
..NET Framework 1.1 configuration settings?

Thanks in advance.
 
use filesystem protection to guarantee that no-one replaces the file.

Thanks for your reply, Dino. The idea is that it is allowed to be replaced,
but only with .NET ones. The second question is that I want to be sure that
it is safe to run it.
 
Maybe you should NOT allow it to be replaced.
instead allow a DLL to be replaced, and the EXE just dynamically loads and
execs the DLL.
This way you can ensure the EXE remains the same.
The DLL may change but it is guaranteed to always be a .NET DLL.

does this work??

-Dino
 
Maybe you should NOT allow it to be replaced.
instead allow a DLL to be replaced, and the EXE just dynamically loads and
execs the DLL.
Click to expand...

Thanks again, Dino. This seems to be the only way, so I think this is what
I'm going to do. However I still hope for a solution with the exe.
 
I guess you could also create a service that copies file from input dir to
dest dir. This service would be a member of a group that only had write
access to that dir or file and would copy it. Expanding that idea, this
service could also do the scheduling for you so you would not need
additional sceduler. Expanding that idea, this .net service could also
check the exe (or dll) by using reflection to make sure it was a .net exe
before it ran and/or copied it.
 
I guess you could also create a service that copies file from input dir to
dest dir. This service would be a member of a group that only had write
access to that dir or file and would copy it. Expanding that idea, this
service could also do the scheduling for you so you would not need
additional sceduler. Expanding that idea, this .net service could also
check the exe (or dll) by using reflection to make sure it was a .net exe
before it ran and/or copied it.
Click to expand...

Thanks William, good idea.
I first need to learn this Reflection namespace, so I better get started :)
 
Back
Top