Assembly in Dot Net C#

Assembly
 --------------------
 Assembly is the final output after
 twice-compilation of all C# codes.
 W.r.t Program Access, assemlies can be
 classified into 2 - types.
 • Private Assembly
 • Shared Assembly.
 Private Assembly
 ---------------------
 The default assembly created is 'private assembly'.
 A private assembly is limited to one application only.
 The private assembly should be kept at \Bin folder
 of an ASP.NET application.
 Shared Assembly
 ---------------------
 A shared Assembly is usable by all applications
 within the system.
 All shared assemblies are LISTED in GAC ['Jack']
  - Global Assembly Cache
 GAC Folder is:
  C:\Windows\assembly\

 A 'private assembly' can be made 'shared assembly'.
 How To Make a Private Assembly - Shared
 -----------------------------------------------------
 Only a 'Strong Named Private Assembly' can be made 'shared'.
 --------
 Step - 1
 ------------
 Generate 'Strong Name' Key Pair
 sn.exe [Strong Naming Utility Tool]
 dos>sn  -k  APPLICATION_PATH\ABC.snk
  Key Pair
   - Private Key [Non-shareable]
   - Public Key [Shareable]
 Step - II
 -------------
 Add the 'Strong Name Key' as META DATA in
 AssemblyInfo.cs File.
 [assembly:AssemblyKeyFile("APPLICATION_PATH\\ABC.snk")]
 Step - III
 -------------
 Re-Build again to get a 'Strong Named Private Assembly'

 Step - IV
 --------------
 Install with GAC
 GacUtil.exe
 dos>gacutil  /i  APPLICATION_PATH\WebAppABC.dll
 Now the assembly is LISTED at C:\Windows\assembly folder.
 dos>gacutil  /l - for listing in DOS mode
 ====

 Meta Data  and Manifest
 ------------------------------
 Meta Data is vital information of an assembly.
 Version Number
 Strong Naming Key
 Company Name
 Product Name
 Title
 Copyright
 Trademark
 All meta data should be written in AssemblyInfo.cs.
 After compilation, all Meta Data of AssemblyInfo.cs
 will be writen into Assembly.
 All meta data will be available in Manifest of the assembly.
 The Manifest can be viewed by ILDASM.exe.

Comments

Post a Comment

Popular posts from this blog

Error : DependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.aem:uber-jar:jar:apis -> version 6.3.0 vs 6.4.0

Image
I got above error after adding dependency in Maven POM xml file placed under newly created AEM arch type and running command  mvn -PautoInstallPackage clean install . Error : DependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.aem:uber-jar:jar:apis -> version 6.3.0 vs 6.4.0 After google and gone through few article I got command ( mvn -PautoInstallPackage -Padobe-public clean install) . Once I run this command this issue with jar compatibility was resolved. Happy Learning!!!
Read more

Operators in Asterisk with Linux

Operators When you create an Asterisk dialplan, you’re really writing code in a specialized scripting language. This means that the Asterisk dialplan—like any programming language—recognizes symbols called operators that allow you to manipulate variables. Let’s look at the types of operators that are available in Asterisk: Boolean operators These operators evaluate the “truth” of a statement. In computing terms, that essentially refers to whether the statement is something or nothing (non-zero or zero, true or false, on or off, and so on). The Boolean operators are: expr1 | expr2 This operator (called the “or” operator, or “pipe”) returns the evaluation of expr1 if it is true (neither an empty string nor zero). Otherwise, it returns the evaluation of expr2. expr1 & expr2 This operator (called “and”) returns the evaluation of expr1 if both expressions are true (i.e., neither expression evaluates to an empty string or zero). Otherwise, it returns zero. expr1 {=,
Read more

ERROR Exception while handling event Sitecore.Eventing.Remote.PublishEndRemoteEventException: System.AggregateExceptionMessage: One or more exceptions occurred while processing the subscribers to the 'publish:end:remote'

I was getting below error while working with cache management on CM and CD server. Actually my code was working fine on CM server but I was not able to access or clear cache object on CD server because of wrong event selection.  PID[18108] Error       ManagedPoolThread #3 16:24:16 ERROR Exception while handling event Sitecore.Eventing.Remote.PublishEndRemoteEventException: System.AggregateExceptionMessage: One or more exceptions occurred while processing the subscribers to the 'publish:end:remote' event.Source: Sitecore.Kernelat Sitecore.Events.Event.EventSubscribers.RaiseEvent(String eventName, Object[] parameters, EventResult result)at Sitecore.Events.Event.RaiseEvent(String eventName, Object[] parameters)at Sitecore.Eventing.Subscription`1.Invoke(Object instance, EventContext context)at Sitecore.Eventing.EventProvider.RaiseEvent(Object event, Type eventType, EventContext context) Above error comes due to wrong event args access in CD server. There are two event args in
Read more