You are creating a class library that will be used in a web application.
You need to ensure that the class library assembly is strongly named.
What should you do?

A.
Use the csc.exe /target:Library option when building the application.

B.
Use the AL.exe command-line tool.

C.
Use the aspnet_regiis.exe command-line tool.

D.
Use the EdmGen.exe command-line tool.

Explanation:
The Windows Software Development Kit (SDK) provides several ways to sign an assembly with a
strong name:
* Using the Assembly Linker (Al.exe) provided by the Windows SDK.
* Using assembly attributes to insert the strong name information in your code. You can use either
the AssemblyKeyFileAttribute or the AssemblyKeyNameAttribute, depending on where the key file
to be used is located.
* Using compiler options such /keyfile or /delaysign in C# and Visual Basic, or the /KEYFILE or
/DELAYSIGN linker option in C++. (For information on delay signing, see Delay Signing an Assembly.)
Note:
* A strong name consists of the assembly’s identity—it’s simple text name, version number, and
culture information (if provided)—plus a public key and a digital signature. It is generated from an
assembly file (the file that contains the assembly manifest, which in turn contains the names and
hashes of all the files that make up the assembly), using the corresponding private key. Microsoft®
Visual Studio® .NET and other development tools provided in the .NET Framework SDK can assign
strong names to an assembly. Assemblies with the same strong name are expected to be identical.