Running at VB.NET program that resides on another computer...

  • Thread starter Thread starter Lars Gaarde
  • Start date Start date
L

Lars Gaarde

Hi everyone....

I have a program written in VB.NET 2003 that is physically placed on a
server.

Several users on the network needs to execute the program from this
location.

I'm getting different errors when trying to launch to program, all of
them security related.

One of the errors tells me to use the ".NET security policy
adminstration tool" to fix this.

I can't seem to find anything like that, so my question is: What do i
have to do to make this work?

Lars G.
 
Unfortunately, this is not something I have delved into yet. But I did
watch a WEBCAST on microsofts site on just that, I recommend you take a
look.

http://support.microsoft.com/default.aspx?scid=fh;EN-US;pwebcst&expand=none


Regards - OHM#



Lars said:
Hi everyone....

I have a program written in VB.NET 2003 that is physically placed on a
server.

Several users on the network needs to execute the program from this
location.

I'm getting different errors when trying to launch to program, all of
them security related.

One of the errors tells me to use the ".NET security policy
adminstration tool" to fix this.

I can't seem to find anything like that, so my question is: What do i
have to do to make this work?

Lars G.
Click to expand...

Regards - OHM# (e-mail address removed)
 
* Lars Gaarde said:
I have a program written in VB.NET 2003 that is physically placed on a
server.

Several users on the network needs to execute the program from this
location.

I'm getting different errors when trying to launch to program, all of
them security related.

One of the errors tells me to use the ".NET security policy
adminstration tool" to fix this.

I can't seem to find anything like that, so my question is: What do i
have to do to make this work?
Click to expand...

<http://www.google.de/[email protected]>

You can distruibute the settings via Active Directory or with
"CasPol.exe" too.
 
Thanks Herfried....

That definately send me in the right direction.

Actually i had already tried this, but didn't realise, that i had to
do this for every DLL and EXE file in the "program" and not just the
main assembly EXE file.

Lars G.
 
Back
Top