-----------------------------------------------------------
New Message on MumbaiUserGroup
-----------------------------------------------------------
From: Swapnil_B1
Message 1 in Discussion
Assembly Benefits & Contents
End users and developers are familiar with versioning and deployment issues
that arise from today's component-based systems. Some end users have
experienced the frustration of installing a new application on their computer,
only to find that an existing application has suddenly stopped working. Many
developers have spent countless hours trying to keep all necessary registry
entries consistent in order to activate a COM class.
Many deployment problems have been solved by the use of assemblies in the .NET
Framework. Because they are self-describing components that have no
dependencies on registry entries, assemblies enable zero-impact application
installation. They also simplify uninstalling and replicating applications.
Versioning Problems
Currently two versioning problems occur with Win32 applications: <o:p></o:p>
Versioning rules cannot be expressed between pieces of an
application and enforced by the operating system. The current approach relies
on backward compatibility, which is often difficult to guarantee. Interface
definitions must be static, once published, and a single piece of code must
maintain backward compatibility with previous versions. Furthermore, code is
typically designed so that only a single version of it can be present and
executing on a computer at any given time.
· There is no way to maintain consistency between sets of
components that are built together and the set that is present at run time.
These two versioning problems combine to create DLL conflicts, where installing
one application can inadvertently break an existing application because a
certain software component or DLL was installed that was not fully backward
compatible with a previous version.
Solution
To solve versioning problems, as well as the remaining problems that lead to
DLL conflicts, the runtime uses assemblies to do the following:
· Enable developers to specify version rules between
different software components.
· Provide the infrastructure to enforce versioning rules.
· Provide the infrastructure to allow multiple versions
of a component to be run simultaneously (called side-by-side execution).
Assembly Contents
In general, a static assembly can consist of four elements:
· The assembly manifest, which contains assembly
metadata.
· Type metadata.
· Microsoft intermediate language (MSIL) code that
implements the types.
· A set of resources.
Only the assembly manifest is required, but either types or resources are
needed to give the assembly any meaningful functionality.
Swapnil (Swaps)
http://swapsnet.spaces.live.com/
-----------------------------------------------------------
To stop getting this e-mail, or change how often it arrives, go to your E-mail
Settings.
http://groups.msn.com/MumbaiUserGroup/_emailsettings.msnw
Need help? If you've forgotten your password, please go to Passport Member
Services.
http://groups.msn.com/_passportredir.msnw?ppmprop=help
For other questions or feedback, go to our Contact Us page.
http://groups.msn.com/contact
If you do not want to receive future e-mail from this MSN group, or if you
received this message by mistake, please click the "Remove" link below. On the
pre-addressed e-mail message that opens, simply click "Send". Your e-mail
address will be deleted from this group's mailing list.
mailto:[EMAIL PROTECTED]
