Microsoft.NET

An assembly is a collection of one or more files grouped together to form a logical unit. The term ?files? in this context generally refers to managed modules, but assemblies can include files that are not managed modules. Most assemblies contain just one file, but assemblies can and sometimes do include multiple files. All the files that make up a multifile assembly must reside in the same directory. When you use the C# compiler to produce a simple EXE, that EXE is not only a managed module, it?s an assembly. Most compilers are capable of producing managed modules that aren?t assemblies and also of adding other files to the assemblies that they create. The .NET Framework SDK also includes a tool named AL (Assembly Linker) that joins files into assemblies.

CLR

See definition for common language runtime.

CLS

See definition for Common Language Specification.

common type system

The specification that determines how the common language runtime defines, uses, and manages types.

common language runtime

The engine at the core of managed code execution. The runtime supplies managed code with services such as cross-language integration, code access security, object lifetime management, and debugging and profiling support.

Common Language Specification (CLS)

A subset of language features that is supported by a broad set of compliant tools. CLS-compliant components and tools are guaranteed to interoperate with other CLS-compliant components and tools. See also: CLS-compliant.

The .NET Assemblies Part1

This online presentation about .NET assemblies helps the webmasters to know about the three tier architecture and about .NET assemblies. The author describes the real need of the three-tier architecture. The author divides the application into three layers named as Presentation, Business Logic and Database. This article describes each with its pictorial representation given.

The .NET Assemblies Part 2

The author defines the assemblies and highlights the benefits of .NET assemblies. The author also discusses about the two developments - Code behind and Custom controls. The author tells that by generating the pre-compiled libraries of IL, the users could improve the performance of their applications. This gives a solution to the beginners thirst to know about .NET assemblies.

The .NET Assemblies Part 3

This article deals with assemblies and their implementation in .NET. The main content of this article is about implementing a simple .NET assembly. In ASP.NET web applications, the users might employ many pre-built assemblies. The author helps by teaching the method of creating their own assemblies. One such creation of the component which would facilitate the users with some options to be viewed as a message or information on the screen. The sample source code is given along with this article.

The automatic memory management scheme employed by the .NET Framework (CLR) is called garbage collection.

Unused memory is automatically reclaimed by garbage collection without interaction with the application

The garbage collector is a low-priority thread that always runs in the background of the application under normal circumstances. It operates when processor time is not consumed by more important tasks. When memory becomes limited, however, the garbage collector thread moves up in priority. Memory is reclaimed at a more rapid pace until it is no longer limited, at which point the priority of garbage collection is again lowered.

in c# memory is divided in five blocks stack,heap,Global,static,& the code block..all the objects created in the heap block(the total size of heap block is 64 mb)whn the heap block is about to full the gc(garbaze collector)automatically invokes & it deletes all those objects which are not in use or not pointing anywhere..in other words we can say dat the GC free the memory by deleting the unused objects or references.

a user never know when GC runs or invokes becz it runs automatically when d heap memory is going to full..

GC takes cares of heap block not stack block so it is good for the user to create any number of objects without care of memory. c# launches new features of garbage collection before c# (in any languages like c or c#)whn a user create a object it thinks first about memory and after dat its user responsibility to free d memory bt this is not d case in c# bcoz GC automatically takes cares of MEMORY MANAGMENT

There are a number of striking differences between ASP.NET and ASP. For some of these differences, the benefits will be immediately obvious. For others. We?ll have to get used to new ways of thinking about dynamic web Pages. Among the changes are:

ASP.NET pages are complied, not interpreted. A binary executable is compiled upon the first request to the page. This image is stored in an in-memory cache on the web server, and subsequent request to this page use this executable to service the request.

The Framework provides a very clean separation of code from content. With ASP, because the HTML is generated as the page is interpreted, your page logic must be embedded into the page at the location where you want the HTML generated by this logic to be output. With ASP.NET, no HTML is generated until all of the code in your page has finished executing. The entire task of HTML generation is done in the page?s rendering step, which uses the properties for all of us who consider script writing and HTML generation a poor substitute to sitting down and writing real code.

ASP.NET Framework maintains state for you. Do you ever have to post of the server to apply validation logic to a data entry HTML form? When there?s a problem, you must write code to repopulate every input on your HTML form. You must also execute script inline to add validation messages next to the fields that have errors. The resulting code is often a tangled mess. If the business logic changes, that?s a tough page to maintain. With the ASP.NET Framework, this state maintenance is done for you. The fields maintain their value without a single line of code written by you. This applies not only to simple text inputs but also to SELECT lists, check boxes, radio buttons, and other input types on your form. Built-in validation controls allow you to enforce your business logic by adding a single tag to your page and simply checking the Page. Is Valid property when it posts to the server.

ASP.NET runs events on the server. In ASP, because of the amount of script that must be mixed with the HTML, it?s common to split a single functional area across several pages. One page may collect data from a user, whereas another accepts the HTTP post and updates your relational data, telling your user the result of the operation. Although its possible to put this functionality into a single ASP page you do so at the risk of needing to maintain a garbled mess of code over the long haul. Breaking these functions into separate pages causes the number of files in your web site to balloon. With ASP.NET, you can set up server side event traps

ASP.NET provides a consistent event model. With ASP, script is executed on the page in a top-down manner. Although it?s possible to put your script within functions that you call from the page body, there?s no event model that fires at specific points in the lifecycle of your page. With ASP.NET, this event model has been added. Most importantly, there?s an event fired whenever your page. With ASP.NET, this event your page begins to load. This is very much like the from_Load event in VB. The page load event can be trapped in a script tag or from your code behind the page. This gives you a consistent model for setting up your output.

script is executed on the page in a top-down manner. Although it?s possible to put your script within functions that you call from the page body, there?s no event model that fires at specific points in the lifecycle of your page. With ASP.NET, this event model has been added. Most importantly, there?s an event fired whenever your page