This article discusses .NET assemblies and strong name signature. In addition to providing some benefits like versioning and giving name uniqueness to an assembly, strong name provides a strong integrity check, and here is the point of this article! By strongly naming an assembly, you are supposed to ensure that your binary has not been tampered with since it was compiled or built.
In self-adaptive systems components are dynamically modified according to the execution environment requirement, where each component is a probable point of failure. Existing approaches to make such systems more vigorous and safe are both brittle and time intensive. A framework for dynamic adaptation has been designed to automate the component integration process at runtime by accessing the equivalent component from a repository of components. The .NET technology allows developers to adapt run-time components by specifying component behavior using pre- and post-assertions on the component's services. Components can be compared for behavioral equivalence by comparing the assertions. These assertions will help us to compute the utility value for each component in the repository and the component with the highest value is picked for replacement. In this paper, we describe the mechanism for component adaptation using .NET services, by considering a system in a dynamic context with proxy switcher and network switcher components
This article focuses on the foundations of .NET programming. It starts with a language primer on the basics; it then covers some more in-depth programming features and language-related IDE enhancements. The article concludes with an overview and map of the .NET Framework class library.