John

• Sep 13th, 2005

 

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.

santhoshkarthiks

 Profile Answers by santhoshkarthiks 

• Nov 14th, 2006

 

Dear Friend,The assembly which is used only by a single application is called as private assembly. Suppose you created a DLL which encapsulates your business logic. This DLL will be used by your client application only and not by any other application. In order to run the application properly your DLL must reside in the same folder in which the client application is installed. Thus the assembly is private to your application.Suppose that you are creating a general purpose DLL which provides functionality which will be used by variety of applications. Now, instead of each client application having its own copy of DLL you can place the DLL in 'global assembly cache'. Such assemblies are called as shared assemblies.