Protection violation

[Deborah]

Hi all -

I assume this is a beta 1 thing, but wanted to be sure ...

I loaded VS.NET on a machine that I don't normally use. Because one never
knows when someone else will use that machine for something else, I save
all of the code to my machine which is on the same network.

With VB.NET, I can create and edit files that reside on my other machine
on the network. However, when I try to run the application I get a protection
violation error when the first form is loaded (I can get the exact message
if someone needs it).

If I copy all of the code to the same machine running VS.NET, the problem
disappears.

Any thoughts?
Thanks -
Deborah

[Bill McCarthy]

Yep, it's a known issue. You can get around it by lowering the security
settings, but that also allows anything over the web for example to run with
local permissions. The best thing as you have already found out, is to copy
to the local machine before running.



"Deborah" <djk@no.com> wrote in message news:3a80ed0b$1@news.devx.com...
>
> Hi all -
>
> I assume this is a beta 1 thing, but wanted to be sure ...
>
> I loaded VS.NET on a machine that I don't normally use. Because one never
> knows when someone else will use that machine for something else, I save
> all of the code to my machine which is on the same network.
>
> With VB.NET, I can create and edit files that reside on my other machine
> on the network. However, when I try to run the application I get a
protection
> violation error when the first form is loaded (I can get the exact message
> if someone needs it).
>
> If I copy all of the code to the same machine running VS.NET, the problem
> disappears.
>
> Any thoughts?
> Thanks -
> Deborah

[Deborah]

Thanks -

I assume this is something that will be fixed?

- DJK

"Bill McCarthy" <Bill_McC@iprimus.com.au> wrote:
>Yep, it's a known issue. You can get around it by lowering the security
>settings, but that also allows anything over the web for example to run
with
>local permissions. The best thing as you have already found out, is to copy
>to the local machine before running.
>
>
>
>"Deborah" <djk@no.com> wrote in message news:3a80ed0b$1@news.devx.com...
>>
>> Hi all -
>>
>> I assume this is a beta 1 thing, but wanted to be sure ...
>>
>> I loaded VS.NET on a machine that I don't normally use. Because one never
>> knows when someone else will use that machine for something else, I save
>> all of the code to my machine which is on the same network.
>>
>> With VB.NET, I can create and edit files that reside on my other machine
>> on the network. However, when I try to run the application I get a
>protection
>> violation error when the first form is loaded (I can get the exact message
>> if someone needs it).
>>
>> If I copy all of the code to the same machine running VS.NET, the problem
>> disappears.
>>
>> Any thoughts?
>> Thanks -
>> Deborah
>
>

[Thomas Eyde]

Why not use SourceSafe or similar, having the database on your computer.
Gives you both worlds: Local code, saved on network.

/Thomas

[Ronald Laeremans [MSFT]]

It will be fixed for Windows Forms applications. It will not be 'fixed' for
applications that do unsafe things, like use P/Invoke to call unmanaged
APIs. It is an integral part of the code security system that you can assign
different levels of trust to code coming from different places. And we will
ship with the default giving limited trust to applications on file shares
(Intranet Zone).

You can give additional trust (using the caspol tool) to code based on a
number of criteria: e.g. you can give additional trust to code on specific
shares, with a specific strong name, with a specific Authenticode
originator.

Ronald Laeremans
Visual C++ compiler team


"Deborah" <djk@no.com> wrote in message news:3a80f87f$1@news.devx.com...
>
> Thanks -
>
> I assume this is something that will be fixed?
>
> - DJK
>
> "Bill McCarthy" <Bill_McC@iprimus.com.au> wrote:
> >Yep, it's a known issue. You can get around it by lowering the security
> >settings, but that also allows anything over the web for example to run
> with
> >local permissions. The best thing as you have already found out, is to
copy
> >to the local machine before running.
> >
> >
> >
> >"Deborah" <djk@no.com> wrote in message news:3a80ed0b$1@news.devx.com...
> >>
> >> Hi all -
> >>
> >> I assume this is a beta 1 thing, but wanted to be sure ...
> >>
> >> I loaded VS.NET on a machine that I don't normally use. Because one
never
> >> knows when someone else will use that machine for something else, I
save
> >> all of the code to my machine which is on the same network.
> >>
> >> With VB.NET, I can create and edit files that reside on my other
machine
> >> on the network. However, when I try to run the application I get a
> >protection
> >> violation error when the first form is loaded (I can get the exact
message
> >> if someone needs it).
> >>
> >> If I copy all of the code to the same machine running VS.NET, the
problem
> >> disappears.
> >>
> >> Any thoughts?
> >> Thanks -
> >> Deborah
> >
> >
>

[Zane Thomas]

On Wed, 7 Feb 2001 12:02:36 -0800, "Ronald Laeremans [MSFT]"
<ronlaere@microsoft.com> wrote:

>You can give additional trust (using the caspol tool)

Uhm, assuming you can figure out how to use that thing. I know y'all have
a UI group over there, can something be done to make caspol usable?


---
Ice Z - Straight Outta Redmond

[Deborah]

Yea, I could. These were just samples I was messing around with - did not
seem worth the effort.

"Thomas Eyde" <thomas.eyde@eunet.no> wrote in message
news:3a8148d2@news.devx.com...
> Why not use SourceSafe or similar, having the database on your computer.
> Gives you both worlds: Local code, saved on network.
>
> /Thomas
>
>