Project won't run from network drive.

  • Thread starter Thread starter Dave Harry
  • Start date Start date
D

Dave Harry

Pardon the crosspost, didn't know where to put this one.

I upgraded a project from VB6 to dotNET 2005.
It compiles and runs ok on a local disk, but if I put the EXE on a mapped
network drive it just apologises for the invonvenience of not running.

Copying the EXE file to the desktop, it works a treat.

A created a blank application (just a new form) and put it on the network
and it executed ok.

What should I do?
 
Hi,

Dave said:
Pardon the crosspost, didn't know where to put this one.

I upgraded a project from VB6 to dotNET 2005.
It compiles and runs ok on a local disk, but if I put the EXE on a mapped
network drive it just apologises for the invonvenience of not running.

Copying the EXE file to the desktop, it works a treat.

A created a blank application (just a new form) and put it on the network
and it executed ok.
Click to expand...

what does your application do? I suppose you collide with the security
policies. Policies for the local intranet are stricter than for the
local machine (the latter is FullTrust by default). The LocalIntranet
zone policy blocks the SQL Client for example (so it is with .Net 1.1, I
don't know about .Net 2.0 in this matter).

hth
Tobi

x-post to m.p.d.g, m.p.d.l.v, m.p.d.l.v.u
fup2 m.p.d.g
 
¤ Pardon the crosspost, didn't know where to put this one.
¤
¤ I upgraded a project from VB6 to dotNET 2005.
¤ It compiles and runs ok on a local disk, but if I put the EXE on a mapped
¤ network drive it just apologises for the invonvenience of not running.
¤
¤ Copying the EXE file to the desktop, it works a treat.
¤
¤ A created a blank application (just a new form) and put it on the network
¤ and it executed ok.
¤
¤ What should I do?

See the following:

How to deploy a .NET Framework application to run from a network location
http://support.microsoft.com/?kbid=832742


Paul
~~~~
Microsoft MVP (Visual Basic)
 
Tobias Schröer said:
Hi,



what does your application do? I suppose you collide with the security
policies. Policies for the local intranet are stricter than for the local
machine (the latter is FullTrust by default). The LocalIntranet zone
policy blocks the SQL Client for example (so it is with .Net 1.1, I don't
know about .Net 2.0 in this matter).

hth
Tobi

x-post to m.p.d.g, m.p.d.l.v, m.p.d.l.v.u
fup2 m.p.d.g
Click to expand...

Basically it's a glorified, but very device specific, terminal program.
The main function of the application is to access serial COM ports. It
creates files on the local computer, downloading and converting data
received from a device. No SQL is involved.

It seems I can add permissions to the project itself, rather than having to
configure something on the client machine? How can I do that?
 
Why are you ignoring my follow up then?
Basically it's a glorified, but very device specific, terminal program.
The main function of the application is to access serial COM ports. It
creates files on the local computer, downloading and converting data
received from a device. No SQL is involved.
Click to expand...

SQL served as an example here. File I/O is not allowed in the (.Net 1.1)
LocalIntranet policy.
It seems I can add permissions to the project itself, rather than having to
configure something on the client machine? How can I do that?
Click to expand...

You can configure each assembly, yes. But you have to do this on the
client machine. If you could deploy custom security settings, the whole
thing would be obsolete.
But there must be ways to deploy a security policy in an automated way.
Sadly, I have none at hand :(


Tobi

x-post to m.p.d.g, m.p.d.l.v, m.p.d.l.v.u
fup2 m.p.d.g
 
Back
Top