Hi There,

I have some doubts about dotnet framework. If someone can please clear it.

I have read...

.Net Framework gives advantage of using dotnet application without registering with system registry. This is made possible due to following reasons

.Net can automatically locate referenced assemblies. It contains manifest which has information about assemblies information with other assemblies.

Does it mean that the folder of dotnet application directory has all referenced files. If so then isn't it waste of diskspace if i already have the file in harddisk in someother location.when a dotnet application is copied from one computer to other it copies all the files even though if they are there. Does it finds out before copying the application wheather all refered dll files are there or not?

Thanking you and waiting for some kind replies.


Amit

Well you need to complete you information Amit.
Registry is no where in the equation if you are talking
.NET assemblies that are created entirely within
.NET and that are gonna be used by an application
made to run on .NET Framework.

There are several ways of looking up for the
assemblies that your application is looking to use.
One is to place it in the application's directory
only and load it from there. This requires no
settings what so ever and such assemblies are
called private assemblies. This is the case that
you queried about in your post and your fear would
have been right if this was the only way.

Assemblies that are commonly used by a number of
applications are stored in a special repository
called GAC (Global Assembly Cache). Any assembly
that’s referred from the GAC, does not get copied to
the applications directory and is used from the GAC only.
Such assemblies are also known as shared assemblies.
Your application can identify what assembly to load from
the GAC using the public/private key matching.

You can even configure assemblies to load from
application directory's subdirectories by doing
appropriate probing settings or from network
locations by doing appropriate codebase settings.

I believe you will be realieved a lot if you would
read about flexibility that assemblies provide you
and while you are on it you might also wanna read
about publisher policies.

Regards
Ankur Verma