.NET clarification of terms

[Daniel Klein]

A recent answer to a post I just made (and a good answer it was) brought up
a question that I found I was not clear on, and I'm sure other .NET'ers
would like to know as well.

What, exactly, is an assembly and how is it different from a 'solution'?
Is it that a 'solution' can contain many 'assemblies'?

Is the term 'assembly' synonymous with 'project'?

The answers to these will certainly turn on that proverbial light bulb ;-)

Daniel Klein
Dublin, Ohio USA

[Lucas Tam]

Daniel Klein <da***********@hotmail.com> wrote in
news:e9********************************@4ax.com:

What, exactly, is an assembly and how is it different from a 'solution'?
Is it that a 'solution' can contain many 'assemblies'?

assembly
A collection of one or more files that are versioned and deployed as a
unit. An assembly is the primary building block of a .NET Framework
application. All managed types and resources are contained within an
assembly and are marked either as accessible only within the assembly or as
accessible from code in other assemblies. Assemblies also play a key role
in security. The code access security system uses information about the
assembly to determine the set of permissions that code in the assembly is
granted. See also: private assembly, shared assembly.

Typically the assembly is the .DLL in your project.
http://msdn.microsoft.com/library/de...l=/library/en-
us/netstart/html/cpgloa.asp

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[Chris Dunaway]

On Fri, 30 Jul 2004 14:42:39 -0400, Daniel Klein wrote:

The answers to these will certainly turn on that proverbial light bulb ;-)

I don't remember a light bulb mentioned anywhere in the book of Proverbs!

:)
--
Chris

dunawayc[AT]sbcglobal_lunchmeat_[DOT]net

To send me an E-mail, remove the "[", "]", underscores ,lunchmeat, and
replace certain words in my E-Mail address.

[Alexandre Moura]

<personal definition alert>
Assemblies are basically individual objects that contain metadata and IL - typically each of your .net Dlls and .exes is an assembly.
A solution is the name given by Visual Studio to an entity that contains a set of projects, with each project creating an assembly when built.
</personal definition alert>

Alex
VB QA Team

--------------------

From: Daniel Klein <da***********@hotmail.com>
Subject: .NET clarification of terms
Date: Fri, 30 Jul 2004 14:42:39 -0400
Message-ID: <e9********************************@4ax.com>
X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: microsoft.public.dotnet.languages.vb
NNTP-Posting-Host: www.featherbrain.net 24.106.233.146
Lines: 1
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.phx.gbl!tk2msftngp13.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.dotnet.languages.vb:220669
X-Tomcat-NG: microsoft.public.dotnet.languages.vb

A recent answer to a post I just made (and a good answer it was) brought up
a question that I found I was not clear on, and I'm sure other .NET'ers
would like to know as well.

What, exactly, is an assembly and how is it different from a 'solution'?
Is it that a 'solution' can contain many 'assemblies'?

Is the term 'assembly' synonymous with 'project'?

The answers to these will certainly turn on that proverbial light bulb ;-)

Daniel Klein
Dublin, Ohio USA