What is the relationship between an assembly and a file?

[nfr]

I understand an assembly is nothing more than a collection of types in a
versioned binary (EXE or DLL) in one or more physical files. Is there any
kind of relationship between the assembly name and the file name it is
housed in. For example, would the assembly name for a .NET file called
"MyRemoteObjects.dll" be "MyRemoteObjects"?

If this is the case, how are multifile assemblies named? Do they take the
name of the file containing the manifest.

[Marc Scheuner [MVP ADSI]]

>I understand an assembly is nothing more than a collection of types in a

versioned binary (EXE or DLL) in one or more physical files. Is there any
kind of relationship between the assembly name and the file name it is
housed in.

What do you mean by "assembly name" ?? The name of a class? The name
of the namespace??

Every class exists within a namespace, and those are totally
independent of file names. You can have namespaces stretched a great
many files. The fully-qualified class name is <namespace>.<class
name>, e.g. "System.Drawing.Color" - is that what you mean?

If so - no, there's no direct or indirect correlation between the
fully-qualified class or namespace name, and the file(s) it's
contained in.

Marc

================================================== ==============
Marc Scheuner May The Source Be With You!
Bern, Switzerland m.scheuner(at)inova.ch

[Mattias Sjögren]

Is there any
kind of relationship between the assembly name and the file name it is
housed in. For example, would the assembly name for a .NET file called
"MyRemoteObjects.dll" be "MyRemoteObjects"?

See the section "Naming Application Components" at

http://msdn.microsoft.com/library/en...emblynames.asp

Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/
Please reply only to the newsgroup.