You work as the application developer at Domain.com.
You are developing a strong-named assembly named Certkiller Ass3.
Certkiller Ass3 will be used by multiple applications.
You plan to frequently rebuild Certkiller Ass3 during the development lifecycle.
Whenever Certkiller Ass3 is rebuilt, you must ensure that it works as expected with all applications that will use it.
You must configure the computer that you are using to create Certkiller Ass3 so that all applications reference the latest build of Certkiller Ass3.
Choose the two actions which you should perform to achieve your goal.
Each correct answer presents only part of the complete solution.
A.
Create a DEVPATH environment variable which points to the build output directory for Certkiller Ass3.
B.
Include this XML element in the computer configuration file:
<developmentMode developerInstallation=”true”/>
C.
Include this XML element in the computer configuration file:
<dependentAssembly>
<assemblyIdentity name=” Certkiller Ass3″
publicKeyToken=”32ab4ba45e0a69a1″
language=”en-US” version=”*.*.*.*” />
<publisherPolicy apply=”no” />
</dependentAssembly>
D.
Include this XML element in the configuration file of each application that must use Certkiller Ass3:
<supportedRuntime version=”*.*.*.*” />
E.
Include this XML element in the configuration file of each application that must use Certkiller Ass3:
<dependentAssembly>
<assemblyIdentity name=” Certkiller Ass3″
publicKeyToken=”32ab4ba45e0a69a1″
language=”en-US” version=”*.*.*.*” />
<bindingRedirect newVersion=”*.*.*.*”/>
</dependentAssembly>
Explanation:
The developmentmode element in the machine configuration file tells the .net runtime to locate the assembly by using the DevPath environment variable. The SupportedRuntime element specifies which .net runtime versions the assembly supports.
The DependentAssembly element is used to encapsulate the binding policy and assembly location for each assembly.
I have the same idea.