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

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

wrote:

"Tobias Schröer" <tobias-schroeerNOSPAM@gmx.de> wrote in message
news:e50vh0$hpt$1@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

> "Tobias Schröer" <tobias-schroeerNOSPAM@gmx.de> wrote in message
> news:e50vh0$hpt$1@news.citykom.de...
>
>>Hi,
>>
>>Dave Harry schrieb:
>>
>>>Pardon the crosspost, didn't know where to put this one.

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

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