Signing in .NET

All about signatures in .NET Here I will describe the different kinds of signing available for your .NET applications and assemblies as well as when and how to use them. Different Kinds of Signatures Briefly, there are two different ways you can sign your .NET assemblies in Windows. It's not immediately obvious from the properties tab, so I'm writing an article encompassing a lot of the details. Strong Name Signing Allows the assembly to be uniquely identified. Can be performed on executables, assemblies, and manifests . Code Signing Authenticates the publisher and ensures code integrity. Strong-Naming Strong-named assemblies A strong name is the combination of name, version number, culture information (optional), processor architecture (optional), public key, and digital signature. These characteristics uniquely identify the assembly, providing many benefits.

Creating a custom configuration section in .NET

How to create a custom type for app.config and web.config in .NET We are creating a configuration for a crazy cat lady. Reference System.Configuration in your project. This contains many of the classes and attributes we will be using. Create a class to represent individual cats, one to represent a collection of cats, and finally one for the lady. The ConfigurationElement class Represents a configuration element within a configuration file. We can define attributes and children by using the ConfigurationProperty attribute on member properties. Here we define a cat type with three attribute properties: name, color, and age. We demonstrate some of the features of ConfigurationPropertyAttribute, marking the latter two as optional, and giving age a default. CatConfiguration.cs using System.Configuration; namespace CatLadyDemo {    public class CatConfiguration :