Skip to main content

Assembly class and Attributes



Namespace: System.Reflection

Assembly attributes provide additional information about an assembly. Typically these attributes are added to AssemblyInfo.cs class.

Class
Description
AssemblyAlgorithmIdAttribute
Specifies an algorithm to hash all files in an assembly. This class cannot be inherited.
AssemblyCompanyAttribute
Defines a company name custom attribute for an assembly manifest.
AssemblyConfigurationAttribute
Specifies the build configuration, such as retail or debug, for an assembly.
AssemblyCopyrightAttribute
Defines a copyright custom attribute for an assembly manifest.
AssemblyCultureAttribute
Specifies which culture the assembly supports.
AssemblyDefaultAliasAttribute
Defines a friendly default alias for an assembly manifest.
AssemblyDelaySignAttribute
Specifies that the assembly is not fully signed when created.
AssemblyDescriptionAttribute
Defines an assembly description custom attribute for an assembly manifest.
AssemblyFileVersionAttribute
Instructs a compiler to use a specific version number for the Win32 file version resource. The Win32 file version is not required to be the same as the assembly's version number.
AssemblyFlagsAttribute
Specifies a bitwise combination of AssemblyNameFlags flags for an assembly, describing just-in-time (JIT) compiler options, whether the assembly is retargetable, and whether it has a full or tokenized public key. This class cannot be inherited.
AssemblyInformationalVersionAttribute
Defines additional version information for an assembly manifest.
AssemblyKeyFileAttribute
Specifies the name of a file containing the key pair used to generate a strong name.
AssemblyKeyNameAttribute
Specifies the name of a key container within the CSP containing the key pair used to generate a strong name.
AssemblyProductAttribute
Defines a product name custom attribute for an assembly manifest.
AssemblyTitleAttribute
Defines an assembly title custom attribute for an assembly manifest.
AssemblyTrademarkAttribute
Defines a trademark custom attribute for an assembly manifest.
AssemblyVersionAttribute
Specifies the version of the assembly being attributed.
CustomAttributeData
Provides access to custom attribute data for assemblies, modules, types, members and parameters that are loaded into the reflection-only context.
CustomAttributeFormatException
The exception that is thrown when the binary format of a custom attribute is invalid.
FieldInfo
Discovers the attributes of a field and provides access to field metadata.
LocalVariableInfo
Discovers the attributes of a local variable and provides access to local variable metadata.
ManifestResourceInfo
Contains manifest resource topology information.
ObfuscateAssemblyAttribute
Instructs obfuscation tools to use their standard obfuscation rules for the appropriate assembly type.
ObfuscationAttribute
Instructs obfuscation tools to take the specified actions for an assembly, type, or member.
ParameterInfo
Discovers the attributes of a parameter and provides access to parameter metadata.
Pointer
Provides a wrapper class for pointers.
PropertyInfo
Discovers the attributes of a property and provides access to property metadata.
ReflectionTypeLoadException
The exception that is thrown by the Module.GetTypes method if any of the classes in a module cannot be loaded. This class cannot be inherited.
StrongNameKeyPair
Encapsulates access to a public or private key pair used to sign strong name assemblies.
TypeDelegator
Wraps a Type object and delegates all methods to that Type.


Assembly.GetCustomAttributes can be used to obtain the custom attributes attached to an assembly.

In AssemblyVersionAttribute <MajorVersion>.<MinorVersion>.<Build>.<Revision>
Build and Revision can be *. But if you specify a revision number, you can’t specify * for build. In build * means an auto-incremented value that is incremented per day. For revision * means any random number.
Labels:

Comments

Post a Comment

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...
Post a Comment
Continue Reading »

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...
Continue Reading »

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...
Post a Comment
Continue Reading »