| .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. |
|
| A C# Grep Application |
| The Code Project |
| Presenting a small C# Application which is providing a Grep like functionality under .NET. |
|
| A System.Security.SecurityException exception occurs when you try to impersonate a user from a secondary thread in an ASP.NET Web application |
| http://www.kbalertz.com/ |
| (842790) - Explains that a SecurityException exception may occur when you try to impersonate a user from a secondary thread in an ASP.NET Web application. Describes three workarounds to solve this problem. |
|
| A System.Security.SecurityException exception occurs when you try to impersonate a user from a secondary thread in an ASP.NET Web application |
| http://www.kbalertz.com/ |
| (842790) - Explains that a SecurityException exception may occur when you try to impersonate a user from a secondary thread in an ASP.NET Web application. Describes three workarounds to solve this problem. |
|
| Automated Generation of Table Columns, Class Properties, and Form Field Mapping with C# Reflection |
| C#Today |
| In this article, Tin Lam shows how to use reflection to help us with complex mappings. Reflection allows us to examine assemblies and types at runtime, and find out everything about that type. We will also see how to dynamically extract the type information, and then carry out automated mappings between database table columns, HTML form fields and class properties. |
|
| CleanUp Files using C# |
| The Code Project |
| This article is just a sample application which uses the .Net framework to delete unwanted files from the directories specified. The Sample uses the System.IO namespace to manage the task and uses a recursive function to delete files. |
|
| 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. |
|
| Error Handling in Visual Basic .NET |
| MSDN |
| Discusses how error handling differs between Visual Basic .NET and Visual Basic 6.0. Main topics include Try/Catch blocks, Exception objects, procedure callers, and how to create your own Exception classes. |
|
| 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 catch exceptions in Visual C++ .NET |
| http://www.kbalertz.com/ |
| (815662) - Catching and dealing with exceptions are standard programming tasks. This article describes how to use a try-catch-finally block to catch an exception. A try-catch-finally block is a wrapper that you put around any code where an exception might occur.... |
|
| How to catch exceptions in Visual C++ .NET |
| Microsoft Support |
| (815662) - Catching and dealing with exceptions are standard programming tasks. This article describes how to use a try-catch-finally block to catch an exception. A try-catch-finally block is a wrapper that you put around any code where an exception might occur.... |
|
| Implementing .NET Role-Based Security without COM+ |
| Egg Head Cafe |
| Security is important. Most developers don't like security. It requires a lot of thought. It requires study. Most developers would rather just "write code", and leave security to "somebody else". Unfortunately, if you are a developer and your job is to produce an application, then guess who that "somebody else" usually is? It's YOU. Even behemoth Microsoft got the message loud and clear. They've made security the single most important thing, above everything else. Wanna know why .NET Server, which was supposed to be released back in March, is delayed until the third quarter? Security! They weren't satisfied, and so they went back to the drawing board, so to speak. And its for real, too. The Microsoft insiders with whom I am privileged to speak with from time to time are totally focused on security. |
|
| Managed Security Context in ASP.NET |
| MSDN |
| In my November 2001 column I focused on the unmanaged security context that is used in an ASP.NET application. It's very important to choose this security context wisely, as any calls to the operating system or to your own unmanaged DLLs and COM components will run here. This month, I'll focus on the way you can make use of your managed security context. |
|
| Managing Directories in .NET |
| http://aspalliance.com/ |
| Using the System.IO namespace you can accomplish many actions such as deleting and copying files and directories. This article covers a few methods for managing file system directories in .NET. |
|
| Multithreaded Programming using C# |
| The Code Project |
| Threading is a lightweight process. With the help of threads we can increase the response time of the application. To use multithreading we have to use the Threading namespace which is included in System. The System.Threading namespace includes everything we need for multi threading. Now lets see the first program. |
|
| PRB: "Requested Registry Access Is Not Allowed" Error Message When ASP.NET Application Tries to Write New EventSource in the EventLog |
| http://www.kbalertz.com/ |
| (329291) - When you use ASP.NET to create a new event source in the event log, you may receive the following error message: System.Security.SecurityException: Requested registry access is not allowed. |
|
| PRB: System.Environment Class Does Not Have a Method to Set the Environment Variable for the Current Process |
| http://www.kbalertz.com/ |
| (829145) - The System.Environment class has methods to read the environment variables. However, this class has no method to set the environment variables for the current process. |
|
| Quick and easy user-level security checks |
| The Code Project |
| A library to manage the low-level details behind user-level security. |
|
| Quick and easy user-level security checks |
| The Code Project |
| A library to manage the low-level details behind user-level security. |
|
| 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.. |
|
| Role Based Security |
| C#Today |
| One of the most common ways of handling authorization is via a technique known as Role Based Security (other techniques use individual user information to grant or deny access). Different variations of role based security have existed in Windows for a long time now. Windows NT and Windows 2000 define built in user groups, such as Administrators, Power Users, etc, and users are granted access to files and network shares based on their Windows group memberships. MTS and COM+ introduced role based security at the application development level, and the .NET framework builds upon this. In this article, Kaushal Sanghavi explores .NETs support for role based security and how it can be used to build a flexible authorization scheme. |
|
| 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. |
|