Answer / sanjeev kumar

Each computer where the common language runtime is
installed has a machine-wide code cache called the global
assembly cache. The global assembly cache stores assemblies
specifically designated to be shared by several
applications on the computer.

You should share assemblies by installing them into the
global assembly cache only when you need to. As a general
guideline, keep assembly dependencies private, and locate
assemblies in the application directory unless sharing an
assembly is explicitly required. In addition, it is not
necessary to install assemblies into the global assembly
cache to make them accessible to COM interop or unmanaged
code.

Note There are scenarios where you explicitly do not
want to install an assembly into the global assembly cache.
If you place one of the assemblies that make up an
application in the global assembly cache, you can no longer
replicate or install the application by using the xcopy
command to copy the application directory. You must move
the assembly in the global assembly cache as well.

There are several ways to deploy an assembly into the
global assembly cache:

* Use an installer designed to work with the global
assembly cache. This is the preferred option for installing
assemblies into the global assembly cache.
* Use a developer tool called the Global Assembly Cache
tool (Gacutil.exe), provided by the .NET Framework SDK.
* Use Windows Explorer to drag assemblies into the
cache.

Note In deployment scenarios, use Windows
Installer 2.0 to install assemblies into the global
assembly cache. Use Windows Explorer or the Global Assembly
Cache tool only in development scenarios, because they do
not provide assembly reference counting and other features
provided when using the Windows Installer.

Administrators often protect the WINNT directory using an
access control list (ACL) to control write and execute
access. Because the global assembly cache is installed in
the WINNT directory, it inherits that directory's ACL. It
is recommended that only users with Administrator
privileges be allowed to delete files from the global
assembly cache.

Assemblies deployed in the global assembly cache must have
a strong name. When an assembly is added to the global
assembly cache, integrity checks are performed on all files
that make up the assembly. The cache performs these
integrity checks to ensure that an assembly has not been
tampered with, for example, when a file has changed but the
manifest does not reflect the change.

Can we extend sealed class in c#?

0 Answers  

---

What's the implicit name of the parameter that gets passed into the set method/property of a class?

0 Answers  

---

What is c# console application?

0 Answers  

---

What is difference between array and list?

0 Answers  

---

Where value types are stored in c#?

0 Answers  

---

---

Explain the clr triggers?

0 Answers  

---

What is anonymous method in c#?

0 Answers  

---

What is a destructor in c#?

0 Answers  

---

What are the differences between static, public and void in c#?

0 Answers  

---

Why do we use abstract class in c#?

0 Answers  

---

What is variable in c#?

0 Answers  

---

What is the difference between var and dynamic types in c# 4.0?

0 Answers  

---