The Sentinel of a Framework
Free Online Web Articles
The Microsoft .NET Framework is among of the many software component that was m manufactured by Microsoft for use of Microsoft Windows operating systems. The .NET Framework is a key Microsoft offering and is intended to be used by most new applications created for the Windows platform.
Its architecture includes the CLI or Common Language Infrastructure, its Assemblies, its Metadatas, its Class Libraries, its Memory Management and especially it’s Security.
The .NET’s security is unique from others is unique. The .NET has its own security mechanism with two general features: Code Access Security (CAS), and validation and verification. Code Access Security is based on evidence that is associated with a specific assembly. Visit the austin .net developer about this.
Typically the evidence is the source of the assembly (whether it is installed on the local machine or has been downloaded from the intranet or Internet). Code Access Security uses evidence to determine the permissions granted to the code.
Other code can demand that calling code is granted a specified permission. The demand causes the CLR to perform a call stack walk: every assembly of each method in the call stack is checked for the required permission and if any assembly is not granted the permission then a security exception is thrown. Check out what the austin .net developer has to offer about this.
When an assembly is loaded the CLR performs various tests. Two such tests are validation and verification. During validation the CLR checks that the assembly contains valid metadata and CIL, and it checks that the internal tables are correct. Verification is not so exact.
The verification mechanism checks to see if the code does anything that is 'unsafe'. The algorithm used is quite conservative and hence sometimes code that is 'safe' is not verified. Unsafe code will only be executed if the assembly has the 'skip verification' permission, which generally means code that is installed on the local machine. See what the austin .net developer has to offer about this.
.NET Framework uses appdomains as a mechanism for isolating code running in a process. Appdomains can be created and code loaded into or unloaded from them independent of other appdomains. This helps increase fault tolerance of the application, as faults or crashes in one appdomain do not affect rest of the application. Appdomains can also be configured independently with different security privileges.
This can help increasing security of the application by separating potentially unsafe code. The developer, however, has to split the application into subdomains; it is not done by the CLR. To learn more about .NET Framework, then visit austin .net developer for details.
Submitting articles has become one of the most popular means of generating quality backlinks and targeted traffic to your website. Join us today - It's Free!
