Assembly

Q1.What do you understand Satellite Assemblies ?
Answer: This assembly is used to get language specific resources for an application.These language-specific assemblies work in side-by-side execution because the application has a separate product ID for each language and installs satellite assemblies in a language-specific subdirectory for each language.

Q2.What do you know about dot NET assemblies?
Answer: Assemblies are the smallest units of versioning and deployment in the dot NET application. Assemblies are also the building blocks for programs such as Web services, Windows services, serviced components, and dot NET remoting applications.

Q3.What is difference private and shared assembly?
Answer: Privateassembly used inside an application only and does not have to be identified by a strong name.
Shared assembly can be used by multiple applications and has to have a strong name.

Q4.What is strong name ?
Answer: A strong name includes name of assembly, version number, culture identity, and a public key token.

Q5.What is assembly ?
Answer: Assemblies are the building blocks of dot NET Framework applications; they form fundamental unit of deployment and version control and reuse and activation scoping, and security permissions. An assembly is a collection of types and resources that are built to work together and form a logical unit of functionality. An assembly provides the common language runtime with the information it needs to be aware of type implementations. To the runtime, a type does not exist outside the context of an assembly.

Q6. How can you debug failed assembly binds ?
Answer: Use the Assembly Binding Log Viewer (fuslogvw.exe) to find out the paths searched.

Q7. Where are shared assemblies stored ?
Answer: Global assembly cache.

Q8. How can you tell the application to look for assemblies at the locations other than its own install ?
Answer: Use the directive in the XML .config file for a given application.

should do the trick. Or you can add additional search paths in the Properties box of the deployed application.

Q9.Where is global assembly cache located on the system ?
Answer: Usually C:\winnt\assembly or C:\windows\assembly.

Q10. How do you specify a custom attribute for the entire assembly (rather than for a class) ?
Answer: Global attributes must appear after any top-level using clauses and before the first type or namespace declarations. An example of this is as follows:
using System;
[assembly : MyAttributeClass] class X {}