| 1: | Indicate whether the following are true or false:
A strongly named assembly must be stored in the GAC. When compiling an application, the CLR automatically searches the GAC for a referenced assembly. When loading an assembly, the CLR automatically searches the GAC for a referenced assembly. A public key token must exist in the manifest of an assembly referencing a strongly named assembly.
|
| 2: | You are developing a component for a class library and want to follow good coding practices. Evaluate the assembly with FxCop. The output includes the following message. What is missing from your code?
TypeName= "AssembliesShouldDeclareMinimumSecurity"
|
| 3: | What are the four parts of an assembly's strong name? |
| 4: | How do you assign a version number to an assembly? How are default values for the build number and revision determined? |
| 5: | What three methods are used to modify a stack walk? Describe the role of each. |
| 6: | What is delayed signing, and why is it used? |
| 7: | Identify each of the following: predefined permission, named permission set, and security zone. |
| 8: | Indicate whether the following statements about assembly deployment are true or false:
Only a strongly named assembly can be placed in the GAC. The <probing> element must specify a directory below the application's base directory. The <codeBase> element is used to redirect the CLR to use a newer version of an assembly. XCOPY deployment can be used to install shared assemblies.
|
| 9: | What element or elements need to be added to this application configuration file so that the application will access the new version 2.0.0.0 of this component, rather than the previous 1.0.0.0 version? Both the application and component reside in c:\data\.
<dependentAssembly>
<assemblyIdentity name="movieclass"
publicKeyToken="1F081C4BA0EEB6DB"
culture="neutral" />
---> Insert code here
</dependentAssembly>
|
