Subscribe to:
Post Comments (Atom)
skip to main |
skip to sidebar
- Bellevue .NET User Group
- This group is an initiative from "Vidya Vrat Agarwal" a .NET Passionate. This group is created with a vision to encourage and help people learn Microsoft .NET technology. This group also provides a platform to share ideas, thoughts and experiences an individual may have while learning and implementing .NET technologies.
Search This Blog
Events / Announcements
Group Presentations Slides / Resources
Articles
- Understanding Bug Triage– Severity & Priority
- What is a Service?
- What is a Web Service?
- Purpose of Metadata
- CLS Compliance - Problem Scenario & Solution
- Chart your Career
- Abstraction and Encapsulation Defined
- Finalizer in .NET
- What .NET is all about
- Code Names
- Father of C#
- Journey through .NET 1.0 to .NET 3.5
- VS 2008 - A solution to long lived coupling between Visual Studio and .NET Framework
Questions & Answers
- Two Main() function in an application?
- What is Managed code?
- What is Metadata and Manifest?
- What is the difference between an Assembly and a Namespace?
- What is versioning? Can Versioning be applied to Private assemblies?
- What is an Exception, how do you achieve Exception Handling in .NET?
- What are the access modifiers C# supports and their purpose?
- What is the difference between Abstract class and an Interface?
- How do you achieve multiple inheritance in .NET?
- What is the advantage of "sealed" keyword in real-world of software development?
- What are the features Inheritance offer above an object creation?
- Would you write your own finalizer/destructor of let .NET GC do the cleanup?
- What is the difference between loading behavior of an .exe and .dll ?
- Why would you choose an .exe over a .dll ?
- Difference between .NET Assembly and a .dll /.exe
Blog Archive
-
▼
2010
(34)
-
▼
April
(21)
- Chart your Career
- What is an Exception, how do you achieve Exception...
- What is versioning? Can Versioning be applied to P...
- What is Metadata and Manifest?
- What is Managed code?
- What is the difference between an Assembly and a N...
- Abstraction and Encapsulation Defined
- Finalizer in .NET
- What are the access modifiers C# supports and thei...
- What is the difference between Abstract class and ...
- How do you achieve multiple inheritance in .NET?
- What is the advantage of "sealed" keyword in real-...
- What are the features Inheritance offer above an o...
- Would you write your own finalizer/destructor or l...
- Limitations of GAC deployed assembly
- How to use a GAC deployed assembly in an application
- Steps to deply an assembly in the GAC
- What is the difference between loading behavior of...
- Why would you choose an .exe over a .dll ?
- Difference between .NET assembly and a .dll/.exe
- Talk on .NET assemblies
-
▼
April
(21)
6 comments:
A Windows DLL or EXE contains library code to be used by ANY program running on Windows. A DLL may contain either structured or object oriented libraries. Its like a repository or library of the programs in the application, that need to the executed.These are language dependent.
DLL expecially are not backward compatible, and hence their use is avoided.i.e when using a newer version of DLL the application may throw an error and it may crash without moving forward.
.NET Technology has tried to erase this issue by storing the DLL or EXE in GAC for Non-.NET compatible applciations.With Microsoft.NET the libraries are stored together with an application in a Global Assembly Cache (GAC).This acts as repository called Global Assemblies to be shared among applications. Assemblies are signed and verified to recognise content modifications. They are identified by name and version to resolve incompatibility issues.
.NET assembly is the component standard specified as COM in .NET terms.
COM (Component Object Model) is the component model based on the object oriented design, which means that the components represented by the COM component exists in the form of CLASSES and OBJECTS. COM components can be used by any .NET compliant languages (VB,C++,C# and VB.NET) running on Windows Operating System;Therefore .NET assemblies are understandable to only Microsoft.NET platform and can be used only in .NET managed applications. There is no compatibility issues when using this.
.Net Assembly includes .dll or .exe along with MetaData and Manifest.
Metadata is the data about data. It describes the instructions, the type of data.
Manifest is the data about assembly - like version information, any dependencies or resources reference information etc...
.Net assembly can be private assembly or can be present in GAC(Global Assembly Cache). Private Assemblies live physically in application folder. Assemblies that live in GAC can be shared among applications.
.NET assembly is a compiled .dll or exe, it can be private or a shared assembly that can be used amongst .NET managed applications thus making it language independent.However, it is platform dependent and can be used only with .NET platform. A .dll is a collection of small programs that can be called by an .exe.
.Net assembly - is a partially compiled code library, which usually generated a CLI language specific code and then compiled into machine language at runtime by the CLR.
.Exe- is a process assembly- respresents a process which will use classes defined in library assemblies (dll).
.Exe -can also use required .net assembly like System Namesapce etc. and create your own assembly.
.net assembly - Is all predefined.
In .NET both exe and dll's are called assemblies.
Assemblies is a logical grouping of one or more modules or resource files as well as they are the smallest units of versioning and deployment in the .NET application.
Assemblies are also the building blocks for programs such as Web services, Windows services, serviced components, and .NET remoting applications.
Assemblies are created by a compiler from source code and set of other files (resource files, etc), and they are used by the CLR - Common Language runtime in .NET to run the application.
A Windows DLL contains library code to be used by any program running on Windows.
A normal/regular DLL/EXE may contain either structured or object oriented libraries.
COM (Component Object Model) is the component model based on the object oriented design, which means that the components represented by the COM component exists in the form of classes and objects implementing a standard specification defined by COM.
COM components can be used by any program running on Windows Operating System; be it is written with VB, C++, Java or even some .NET compliant language like C# and VB.NET.
Dot NET assembly is the component standard specified by the .NET. Hence, dot net assemblies are understandable to only Microsoft.NET and can be used only in .NET managed applications.
when you implement a Assembly (DLL) in a .NET Language (e.g. C#, VB.NET,...) you produce a managed assembly.
A managed assembly contains managed code and is executing by the .NET Runtime.
When you create a DLL with C++ or VB 6.0 you produce a win32 / com DLL.If you use this dll in a .NET Program, the Visual Studio create automatically a INTEROP file for you, so you can call the "unmanaged" dll from manage code (.NET Runtime Code).
With a managed assembly (i.e .NET) you have all advantages of the .Net runtime, e.g.: Code Access Security (CAS), Garbage Collection (GC), ...
For using a managed assembly (.Net Assembly) is the simplest option to copy the dll to the bin folder. Other "old" COM Components must you register with the "regsvr32" tool.
Post a Comment