Comments on: .NET Assembly FAQ – Part 1

By: kaka4.......

kaka4....... — Sat, 18 Dec 2010 09:27:27 +0000

The assembly is an important element of .NET programming. On the .NET platform, an assembly is a unit of reuse, versioning, security and deployment.an application, they must be placed into modules that are part of an assembly. Every managed application in .NET is deployed as an assembly. It means that the entire .NET code on compilation gets converted into an Intermediate Language (IL) code and gets stored as an assembly. In addition to the IL code, an assembly also contains Assembly metadata (Manifest), Type metadata and Resources.
If an assembly is to be made up of several programs, the programs can be stored in separate modules. Suppose there are two source files a.cs and b.cs of which, a.cs is stored in a module, whereas, ‘b.cs’ is stored in the assembly itself. Both comprise an assembly named mydll.dll.

By: pks007

pks007 — Sat, 18 Dec 2010 09:04:44 +0000

I m so confused that what is actually an assembly and what is the purpose of using assembly?can we create an assembly for an application?what is difference b/w assembly and namspace plz tell me??

By: Andy

Andy — Fri, 12 Nov 2010 05:33:12 +0000

Question: What are functions performed by an assembly?
A. It contains code that the CLR executes.
B. It forms a security boundary.
C. It’s the smallest unit of code.
D. It’s the unit at which side-by-side execution is supported.
E. It forms a version boundary.

Answer: ???

By: ih-77

ih-77 — Mon, 18 Oct 2010 08:56:19 +0000

“The assembly manifest is required; the other elements are optional.”

Do you mean that the source code is not required?

By: timm

timm — Sun, 15 Aug 2010 16:56:25 +0000

@Christian: Yes, a single namespace can span across multiple assemblies. Of course you’ll want to ensure that you don’t have any duplicate type names or you’ll get an ambiguous definition error.

By: christian

christian — Sun, 15 Aug 2010 16:52:02 +0000

Yeah 3000 files in one project is huge. This Application has more than 100 total projects. The specific project that holds 3000 files is basically holding (copybooks) datasets for transmitting data from the CICS server side DB2 storage to the desktop application and vice-verca.

The other 100 projects use the Schema project to access the dataset (particular data layout). If I break the 3000 files out to 6 different projects (based on different products) is there a way to access the different assemblies under on namespace. So, if the 6 new projects are called Project.Schema1, Project.Schema2…. etc… Can I access the 6 different schemas and there xsd’s using one namespace called “SCHEMA”. The xsd’s are unique.

By: timm

timm — Sun, 15 Aug 2010 15:06:24 +0000

@Christian: 3000 files is a massive project! Not only is it unwieldly to manage and takes too long to compile, it’s probably rife with dependency issues.

Ideally the project should be subdivided into multiple smaller projects. Create a dependency tree to help guide you. Just like an inheritance tree, the project dependencies ideally should flow in a single direction (so there are no circular dependencies). Good luck!

By: christian

christian — Sat, 14 Aug 2010 00:25:05 +0000

if I have a solution with multiple projects and one of those projects (a schema holding project) holds about 3000 files what is the best way to break this up to decrease compile time. I’m currently trying to break the one schema project out to five project schema files ( based on business differences). I’m current using vs5 on XP – 32 bit. Is this the best way to go or is there a better way.

By: hari

hari — Tue, 20 Apr 2010 09:44:23 +0000

fantus article, best i had ever read. keep it up, god bless you.

By: kasi

kasi — Sat, 10 Apr 2010 12:26:14 +0000

Five(5) types of assemblies:

1. Single File
2. Multifile
3. Private
4. Shared
5. Sattelite