Project won't run from network drive.

[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?

--
Dave Harry

[Tobias Schröer]

Hi,

Dave Harry schrieb:

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 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

[Patrice]

..NET also handles security in a way similar to IE "zones". By default code
running from the network doesn't have the right to perform all operations...

Look around
http://msdn.microsoft.com/library/de...figuration.asp

--
Patrice

"Dave Harry" <Da*******@please.keep.replies.in.the.newsgroup> a écrit dans
le message de news: u6**************@TK2MSFTNGP04.phx.gbl...

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?

--
Dave Harry

[Paul Clement]

On Wed, 24 May 2006 15:13:56 +1000, "Dave Harry" <Da*******@please.keep.replies.in.the.newsgroup>
wrote:

¤ 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)

[Dave Harry]

"Tobias Schröer" <to*******************@gmx.de> wrote in message
news:e5**********@news.citykom.de...

Hi,

Dave Harry schrieb:

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 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

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?
--
Dave Harry

[Tobias Schröer]

Dave Harry schrieb:

"Tobias Schröer" <to*******************@gmx.de> wrote in message
news:e5**********@news.citykom.de...

Hi,

Dave Harry schrieb:

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

Why are you ignoring my follow up then?
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).
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.

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?

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

[Dave Harry]

Why are you ignoring my follow up then?

I assure you Tobias, I am not deliberately ignoring anything you say, but
take all suggestions gratefully.
If you have posted other comments elsewhere I've not seen them. Or perhaps I
have misread you.

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).

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.

SQL served as an example here. File I/O is not allowed in the (.Net 1.1)
LocalIntranet policy.

Understood. I can see that the COM port IO is causing the same security
issue.

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?

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 :(

Surely it can't be this hard?! Even an old hyperterminal program from last
century can be run from a network location.
Can I not do the same thing in dot net? I want to release this software;
having users go through config wizards is not what I had in mind.

--
Dave Harry