Assemblies are the smallest units of versioning and deployment
in the .NET application. Assemblies are also the building blocks for programs
such as Web services, Windows
services, serviced components, and .NET remoting applications.
A strong name includes the
name of the assembly, version number, culture identity, and a public key token.
Use the directive in the XML .config file for a given
application.
<probing
privatePath="c:\mylibs; bin\debug” />
should
do the trick. Or you can add additional search paths in the Properties box of the deployed application.
Use publisher policy. To configure a publisher
policy, use the publisher policy configuration file, which uses a format similar app .config file. But unlike the app .config file, a publisher policy file needs to be compiled into an assembly and placed in the GAC.
Delay signing allows you to place a shared
assembly in the GAC by signing the assembly with just the public key. This allows the assembly to be signed with the private key at a later stage, when the development process is complete and the component or assembly is ready to be deployed. This process enables developers to work with shared assemblies as if they were strongly named, and it secures the private key of the signature from being accessed at different stages of development. |
A Blog For MicroSoft Technologies Visual Studio .Net, SQL Server Developers.
Thursday, 20 December 2012
ASP.NET Interview Question Answers For Deployment questions
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
Comment Here