.NET 1.1 security policies not functioning when .NET 2.0 is installed
- From: "Jeremie" <JeremieForKevin@xxxxxxxxxxxxxxxxx>
- Date: Thu, 8 Dec 2005 15:04:22 -0700
Hi,
We had a Runtime Security Policy Code Group created in .NET 1.1
Configuration to give Full Access to a folder on a network share. When we
installed .NET Framework 2.0, the policy quit working and our application
could no longer initialize the .NET Framework.
I have the following questions as to what happened and how to resolve the
issue:
1. Is the problem that now our application is attempting to initialize
through .NET Framework 2.0 and the security policy is only for .NET
Framework 1.1?
2. Is there a way to force our application to initialize through .NET
Framework 1.1?
3. Is there something else we are missing that is causing the .NET Framework
1.1 security policy to be ignored?
4. If ran CasPol.exe in the .NET Framework 2.0 with the same switches we
used in .NET Framework 1.1, will this fix the issue?
Thanks,
Jeremie
.
- Follow-Ups:
- Re: .NET 1.1 security policies not functioning when .NET 2.0 is installed
- From: Michael Willers
- Re: .NET 1.1 security policies not functioning when .NET 2.0 is installed
- Prev by Date: Re: .Net 2.0 signing TCP channel - examples or guidance?
- Next by Date: exception inside lock before lock body
- Previous by thread: .Net 2.0 signing TCP channel - examples or guidance?
- Next by thread: Re: .NET 1.1 security policies not functioning when .NET 2.0 is installed
- Index(es):
Relevant Pages
|