What should you do?

You are currently in the process of creating a shared assembly.
You are required to perform many integration tests to make sure the assembly works properly with multiple applications.
You want to avoid constantly updating each application’s reference when the assembly is updated.
You have set the DEVPATH environmental variable to the default build location for the shared assembly.
You need to ensure that the Common Language Runtime (CLR) uses DEVPATH to locate the shared assembly.
What should you do?

A.
Add the following element to each application’s application configuration file:
<dependentAssembly>
<assemblyIdentity name=”SharedAssembly” />
<codeBase version=”1.0.0.0″ DEVPATH =”true” />
</ dependentAssembly >

B.
Add the following element to the machine.config file in the development computer:
<dependentAssembly>
<assemblyIdentity name=”SharedAssembly” />
<codeBase version=”1.0.0.0″ DEVPATH =”true” />
</ dependentAssembly >

C.
Add the following element to each application’s application configuration file:
<configuration>
<runtime>
<developmentMode developerInstallation=”true” />
</runtime>
</configuration>

D.
Add the following element to the machine.config file in the development computer:
<configuration>
<runtime>
<developmentMode developerInstallation=”true” />
</runtime>
</configuration>

Explanation:

The developmentMode element instructs the CLR to use the DEVPATH environmental variable to locate assemblies.
If you do not add this element to the machine.config file, the DEVPATH environmental variable will be ignored.

Incorrect Answers:
A, C: Application configuration files are used for application-specific settings only
B: The codeBase element does not have a DEVPATH attribute.