the project location is not fully trusted by .net runtime

microsoft.public.dotnet.languages.vb

28 Feb 2005 3:59 PM

Quan

I have a solution with several vb.net projects in it. I
developed the code in one machine then copied all the
files in the other machine to continue the development.
The projects are on the local drivers (E driver on the
first machine and C driver on the second). When I try to
open the projects on the second machine, I got:
The project location is not fully trusted by .net
runtime. This is usually because it it either a network
share or mapped to a network share not on the local
machine.
Since I am not dealing with network location here, I
guess it is because of the different driver's names???
I have been transferred those projects between the two
computers for quite a while. The problem suddenly
appears. Could someone help? Thanks. Quan

28 Feb 2005 5:49 PM

Brian Swanson

If you are accessing the same files on two different machines the you
must be using a network of some sort. I would assume that E: drive on
the first machine is actually a mapped drive to the C: drive on the
second machine.

The easiest way to resolve this is to adjust the .NET security for the
Local Intranet zone to allow your machine to trust the code that's
running from another machine on your local network.

You can make this adjustment by running the .NET Framework Wizard in
your Control Panel.

Hope this helps,
Brian Swanson

Show quoteHide quote

"Quan" <hollyl***@yahoo.com> wrote in message news:hollyli21@yahoo.com:
> I have a solution with several vb.net projects in it. I
> developed the code in one machine then copied all the
> files in the other machine to continue the development.
> The projects are on the local drivers (E driver on the
> first machine and C driver on the second). When I try to
> open the projects on the second machine, I got:
> The project location is not fully trusted by .net
> runtime. This is usually because it it either a network
> share or mapped to a network share not on the local
> machine.
> Since I am not dealing with network location here, I
> guess it is because of the different driver's names???
> I have been transferred those projects between the two
> computers for quite a while. The problem suddenly
> appears. Could someone help? Thanks. Quan

28 Feb 2005 10:55 PM

Quan

Sorry I didn't make it clear enough. I am not accessing
the same files from two different machines. I copy the
whole files over. So I do some development on machine 1,
copy the files to machine 2 then start working on machine
2. I guess when I copy the files over to machine 2, some
info about the file paths on machine 1 is carried over
but I just couldn't find them.
Thanks.
Quan

>-----Original Message-----
>If you are accessing the same files on two different

machines the you

>must be using a network of some sort. I would assume

that E: drive on

>the first machine is actually a mapped drive to the C:

drive on the

>second machine.
>
>The easiest way to resolve this is to adjust the .NET

security for the

>Local Intranet zone to allow your machine to trust the

code that's

>running from another machine on your local network.
>
>You can make this adjustment by running the .NET

Framework Wizard in
Show quoteHide quote

>your Control Panel.
>
>Hope this helps,
>Brian Swanson
>
>"Quan" <hollyl***@yahoo.com> wrote in message
news:hollyli21@yahoo.com:
>> I have a solution with several vb.net projects in it. I
>> developed the code in one machine then copied all the
>> files in the other machine to continue the development.
>> The projects are on the local drivers (E driver on the
>> first machine and C driver on the second). When I try
to
>> open the projects on the second machine, I got:
>> The project location is not fully trusted by .net
>> runtime. This is usually because it it either a network
>> share or mapped to a network share not on the local
>> machine.
>> Since I am not dealing with network location here, I
>> guess it is because of the different driver's names???
>> I have been transferred those projects between the two
>> computers for quite a while. The problem suddenly
>> appears. Could someone help? Thanks. Quan
>
>.
>

28 Mar 2005 4:35 PM

vinnydavi

Quan wrote:
Show quoteHide quote

> Sorry I didn't make it clear enough. I am not accessing
> the same files from two different machines. I copy the
> whole files over. So I do some development on machine 1,
> copy the files to machine 2 then start working on machine
> 2. I guess when I copy the files over to machine 2, some
> info about the file paths on machine 1 is carried over
> but I just couldn't find them.
> Thanks.
> Quan
> >-----Original Message-----
> >If you are accessing the same files on two different
> machines the you
> >must be using a network of some sort. I would assume
> that E: drive on
> >the first machine is actually a mapped drive to the C:
> drive on the
> >second machine.
> >
> >The easiest way to resolve this is to adjust the .NET
> security for the
> >Local Intranet zone to allow your machine to trust the
> code that's
> >running from another machine on your local network.
> >
> >You can make this adjustment by running the .NET
> Framework Wizard in
> >your Control Panel.
> >
> >Hope this helps,
> >Brian Swanson
> >
> >"Quan" <hollyl***@yahoo.com> wrote in message
> news:hollyli21@yahoo.com:
> >> I have a solution with several vb.net projects in it. I
> >> developed the code in one machine then copied all the
> >> files in the other machine to continue the development.
> >> The projects are on the local drivers (E driver on the
> >> first machine and C driver on the second). When I try
> to
> >> open the projects on the second machine, I got:
> >> The project location is not fully trusted by .net
> >> runtime. This is usually because it it either a network
> >> share or mapped to a network share not on the local
> >> machine.
> >> Since I am not dealing with network location here, I
> >> guess it is because of the different driver's names???
> >> I have been transferred those projects between the two
> >> computers for quite a while. The problem suddenly
> >> appears. Could someone help? Thanks. Quan
> >
> >.
> >

I just experienced this same issue. The Solution and Project files were
developed on another machine, and I copied them. Although I still don't
know the cause, nor do I know what encouraged me to do so, but if you
view the .proj file (.vbproj or .csproj) look at your namespace
setting. Although my project name was "Components", I had my namespace
set to "MyCompany.Components". What I did was changed the namespace in
the project file to "Components" giving it the same name as the project
file. I did this in notepad. Then Open the project in VS.NET. You'll
still get the error, but save the project. Now open the proj file again
in notepad, change your namespace back to what you want
"MyCompany.Components". Save from notepad, reopen project in VS .NET
and the error is gone.

I've copied projects before and haven't seen this behavior, except I
used to store them in My Documents - My Projects. The directory I'm
working under now under a sub folder off the root of C:\.

-Vinny Davi
MCSD.NET