| .NET |
| MSDN |
| Unexpected Errors in Managed Applications |
|
| .NET Security |
| C# Corner |
| I basically wanted to programmatically check whether the user had the relevant permissions by accessing their windows account. Fortunately, .NET provides this through the System.Security.Principal namespace. I also wanted to deny access to particular drives - this is done through the namespace System.Security.Permissions. |
|
| Choosing Among File I/O Options in Visual Basic .NET |
| MSDN |
| This article is aimed at the Visual Basic programmer who may be confused by the multiplicity of ways to approach file I/O in Visual Basic .NET. Available alternatives include the methods provided in the Visual Basic .NET runtime, the FileSystemObject, and the methods furnished in the common language runtime. Upon completion, the experienced developer will be familiar with all three and will be equipped to make choices among them. |
|
| Code Access Permissions |
| MSDN |
| Code access permissions are permission objects that are used to protect resources and operations from unauthorized use. They are a fundamental part of the common language runtime's mechanism for enforcing security restrictions on managed code. |
|
| Code Access Security |
| C#Today |
| With the .NET strategy evangelizing loosely coupled component development, the designers of .NET had to come up with security strategies that helped to control these potentially dangerous components. The .NET framework introduces two main models for securing your application: code based security, and role based security. In this article, the first of a week-long topic on security, Kaushal Sanghavi discusses the .NET frameworks for security, and demonstrates how we can use permissions in code. Later in the week, he will also tackle custom security permissions, custom security implementation, and integrating COM+ and .NET security schemes. |
|
| Code Access Security from the perspective of the Developer and Administrator |
| The Code Project |
| Looking at Code Access Security From the Perspective of the Developer and Administrator |
|
| Custom Permissions |
| C#Today |
| Any multi user system needs to have a concept of security to protect one users data from another. This security element could be anything from granting or denying a user access to a file, a network share, or certain entities in a database. These security mechanisms are controlled via the use of Permissions. Before the advent of .NET, using permissions in application code was hard, but now the framework allows a very open and extensible permission architecture. In this article, the third of the week's security-based articles, Kaushal Sanghavi explores the support that the .NET framework offers for working with permissions, and demonstrate how developers can design their own custom permissions to control access to protected data. |
|
| Host Secure, Lightweight Client-Side Controls in Microsoft Internet Explorer |
| MSDN |
| With all the talk about Microsoft® .NET these days, it's natural for developers to look to this new platform for alternatives to traditional client-side Web technologies, such as ActiveX®. While the immediate impact of .NET is greatest on the server, corporate intranet developers targeting Microsoft Internet Explorer 5.01 or higher can use .NET Windows® Forms technology to build lightweight, zero-impact, secure client-side objects that can utilize the powerful .NET Framework.
|
|
| How to use the AllowPartiallyTrustedCallers attribute to call an assembly that has a strong name from a Web page by using Visual C# .NET |
| http://www.kbalertz.com/ |
| (839300) - Describes how to call a Windows user control from a Web page. This user control is built as an assembly that has a strong name, and the user control is built by using the AllowPartiallyTrustedCallers attribute in the assembly. |
|
| HOW TO: Implement a Managed Component that Wraps the Browse For Folder Common Dialog Box by Using Microsoft Visual Basic .NET |
| http://www.kbalertz.com/ |
| (811004) - This step-by-step article describes how to write a design time component that wraps the Browse For Folder common dialog box. |
|
| Return of the Rich Client: Code Access Security and Distribution Features in .NET Enhance Client-Side Apps |
| MSDN |
| Rich clients employ many of the features and conveniences of the operating system they run on, and the list of these features has been growing since the dawn of the PC. But as apps have migrated to the Web, the trend towards increasing client-side functionality has ground to a virtual halt. There are several reasons for this; chief among them are security and deployment problems. But that's all about to change. With the .NET Framework, you can participate in building the distributable rich client of the future. In this article, the author enumerates the pertinent features of .NET that will allow you to build safe, easily deployable controls. The features discussed include managed code, code access security, versioning control, Windows Forms classes, and isolation.. |
|
| Security Briefs: Beware of Fully Trusted Code |
| MSDN |
| Understand the implications of fully trusted code. |
|
| Security in .NET: Enforce Code Access Rights with the Common Language Runtime |
| MSDN |
| Component-based software is vulnerable to attack. Large numbers of DLLs that are not tightly controlled are at the heart of the problem. Code access security in the Common Language Runtime of the Microsoft .NET Framework addresses this common security hole. In this model, the CLR acts as the traffic cop to assemblies, keeping track of where they came from and what security restraints should be placed on them. Another way the .NET Framework addresses security is by providing preexisting classes which have built-in security. |
|
| Understanding .NET Code Access Security |
| C# Corner |
| When we are running an application and we need to run a feature for which, the application does not have the relevant module, the application connects to the Internet and downloads the module into the Global Assembly Cache (GAC) and begins executing. This is done without being prompted to us. |
|
| Utilize the full functionality of Whidbey File Management from VB.NET |
| The Code Project |
| Article on Whidbey File Management |
|
