Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Security Exceptions during debug of .NET application
| Article ID | : | 951595 |
| Last Review | : | April 10, 2008 |
| Revision | : | 1.3 |
Source: Microsoft Support
Back to the top
RAPID PUBLISHING
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Back to the top
Action
A .NET project is located and debugged from a mapped drive. The project has code that attempts to perform any of the following type operations: File IO, Registry, Performance Counter or Event Log.
Back to the top
Result
The assembly throws a SecurityException while debugging.
For example the following code is attempting to read a directory:
string[] cFiles = Directory.GetFiles(@"C:\");
The result is a SecurityException stating:
Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
Back to the top
Cause
The project is not trusted. It is considered to be in the Intranet zone and the default permission set for the Intranet Zone blocks certain accesses including File IO, Registry, Performance Counter and Event Log as well as several other permission types. This is a Code Access Security function.
When originally attempting to open the project from the shared location a Visual Studio message "The project location is not trusted:" is displayed. However, this message can be disabled from the same dialog, and therefore subsequent attempts may not be provided this information.
Back to the top
Resolution
There are several potential resolutions to this issue:
| 1. | (Preferred) Copy the project to a drive that is local to your Visual Studio installation.
|
| 2. | Update your Code Access Security policy with the Caspol tool or by using the .NET Framework Configuration tool
| 1. | Alter the permission set in the All_Code section of the LocalIntranet_Zone.
| | 2. | Add a new code group for the assembly, providing it with a permission set appropriate for the necessary access |
|
Back to the top
More Information
.NET Framework Developers Guide (Code Access Security) (http://msdn2.microsoft.com/en-us/library/930b76w0.aspx)Caspol: Code Access Security Policy editor (http://msdn2.microsoft.com/en-us/library/cb6t8dtz.aspx)Back to the top
DISCLAIMER
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Back to the top
APPLIES TO
| • | Microsoft .NET Framework 1.0 |
| • | Microsoft .NET Framework 1.0 Service Pack 3 |
| • | Microsoft .NET Framework 1.1 Service Pack 1 |
| • | Microsoft .NET Framework 2.0 |
| • | Microsoft .NET Framework 2.0 IA64 Edition |
| • | Microsoft .NET Framework 2.0 Software Development Kit |
| • | Microsoft .NET Framework 2.0 x64 Edition |
| • | Microsoft .NET Framework 3.0 |
| • | Microsoft .NET Framework 3.5 |
| • | Microsoft .NET Framework Class Libraries 2.0 |
| • | Microsoft .NET Framework 1.1 |
| • | Microsoft Visual Studio .NET 2002 Academic Edition |
| • | Microsoft Visual Studio .NET 2002 Enterprise Architect |
| • | Microsoft Visual Studio .NET (2002), Enterprise Architect Edition SP1 |
| • | Microsoft Visual Studio .NET 2002 Professional Edition |
| • | Microsoft Visual Studio .NET 2003 Service Pack 1 |
| • | Microsoft Visual Studio .NET 2003 Enterprise Developer |
| • | Microsoft Visual Studio .NET 2003 Enterprise Architect |
| • | Microsoft Visual Studio .NET 2003 Academic Edition |
| • | Microsoft Visual Studio .NET 2002 Enterprise Developer |
| • | Microsoft Visual Studio .NET 2002 Service Pack 1 |
| • | Microsoft Visual Studio Team System 2008 Team Suite |
| • | Microsoft Visual Studio 2008 Standard Edition |
| • | Microsoft Visual Studio 2008 Professional Edition |
| • | Microsoft Visual Studio 2008 Academic Edition |
| • | Microsoft Visual Studio 2005 Team Suite |
| • | Microsoft Visual Studio 2005 Standard Edition |
| • | Microsoft Visual Studio 2005 Professional Edition with MSDN Professional Subscription |
| • | Microsoft Visual Studio 2005 Professional Edition with MSDN Premium Subscription |
| • | Microsoft Visual Studio 2005 Professional Edition |
Back to the top
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please