Max wrote:
Is an assembly file a dll file or can it also be an executable file?
An assembly is a general term for one or more files. It is a unit of
security, a unit of deployment and a unit of type declaration. It can
have one or more code files (called modules) and it can have zero or
more resource files. So if you deploy an assembly you must deploy all of
the code files and all of the resource files in one action. If you
change the trust for the assembly then all types in all the code modules
will have that trust.
One module will have a data section called the manifest which contains
information about all the other files in the assembly. The code files
(at the moment, according to the CLI spec) are Portable Executable (PE
files) which means they can be libraries or process files. The extension
is fairly irrelevent, because the loading mechanism will look for a file
with the specified name with either an extension of .dll or .exe.
Modules, other than the one that contains the manifest, can have
whatever extension you like (the convention is .netmodule).
Richard
--
http://www.grimes.demon.co.uk/workshops/fusionWS.htm http://www.grimes.demon.co.uk/workshops/securityWS.htm 
