Redirected profiles and VS2003/.NET v.1.x

[B. Hummer]

My corporate environment uses redirected profiles for Application Settings,
My Documents and Desktop. I've already gotten through the fact that to run my
apps "trusted" that I need to have the build directory on my local PC and not
in my redirected My Documents (\\servername\redirect\username\My Documents\).
Now I'm running into a new problem.

VS2003 / .NET v1.x stores the user's security.config in the Application
Settings folder of the user's profile. For me this is redirected to a share
on a file server. Because of this (I believe) I'm finding the User branch of
the Runtime Security Policy (.NET Configuration 1.1) to be read only. I need
to be able to modify this so I can use the Office tools for VS.NET.

(Note: Interestingly, the path that .NET Configuration 1.1 is looking for
the security.config file, \\servername\redirect\username\Application
Data\Microsoft\CLR Security Config\v1.1.4322\security.config doesn't exist.
The hierarchy goes down to the Microsoft folder but stops there.)

[B. Hummer]

Still haven't found a solution to this one.

"B. Hummer" wrote:

My corporate environment uses redirected profiles for Application Settings,
My Documents and Desktop. I've already gotten through the fact that to run my
apps "trusted" that I need to have the build directory on my local PC and not
in my redirected My Documents (\\servername\redirect\username\My Documents\).
Now I'm running into a new problem.

VS2003 / .NET v1.x stores the user's security.config in the Application
Settings folder of the user's profile. For me this is redirected to a share
on a file server. Because of this (I believe) I'm finding the User branch of
the Runtime Security Policy (.NET Configuration 1.1) to be read only. I need
to be able to modify this so I can use the Office tools for VS.NET.

(Note: Interestingly, the path that .NET Configuration 1.1 is looking for
the security.config file, \\servername\redirect\username\Application
Data\Microsoft\CLR Security Config\v1.1.4322\security.config doesn't exist.
The hierarchy goes down to the Microsoft folder but stops there.)

[B. Hummer]

Figured this one out on my own. The full path listed below to the config
files did not exist. Manually creating them and then launching mscorcfg.msc
built the necessary files and "unlocked" the approriate section.

"B. Hummer" wrote:

Still haven't found a solution to this one.

"B. Hummer" wrote:

My corporate environment uses redirected profiles for Application Settings,
My Documents and Desktop. I've already gotten through the fact that to run my
apps "trusted" that I need to have the build directory on my local PC and not
in my redirected My Documents (\\servername\redirect\username\My Documents\).
Now I'm running into a new problem.

VS2003 / .NET v1.x stores the user's security.config in the Application
Settings folder of the user's profile. For me this is redirected to a share
on a file server. Because of this (I believe) I'm finding the User branch of
the Runtime Security Policy (.NET Configuration 1.1) to be read only. I need
to be able to modify this so I can use the Office tools for VS.NET.

(Note: Interestingly, the path that .NET Configuration 1.1 is looking for
the security.config file, \\servername\redirect\username\Application
Data\Microsoft\CLR Security Config\v1.1.4322\security.config doesn't exist.
The hierarchy goes down to the Microsoft folder but stops there.)