Domain.com uses Visual Studio.NET 2005 as its application development platform.
You are developing a .NET Framework 2.0 application and are busy developing the shared assembly called BillSharedObjects which resides in a file named BillSharedObjects.dll, upon compiling you store the assembly in the C:BillSharedObjectsDebug directory.
You do not want the assembly to be repeatedly installed in the global assembly cache while you develop and debug.
You want the application to load the assembly from its current location by .Net Framework when testing whilst any changes made to the system not affect any other applications that are deployed or will be deployed.
What should you do? (Choose two)
A.
C:SharedObjectsDebug must be put in the PATHEXT environment variable
B.
C:SharedObjectsDebug must be put in the PATH environment variable
C.
C:SharedObjectsDebug must be put in the DEVPATH environment variable
D.
The following code should be added to the application configuration file:
<configuration>
<runtime>
<assemblyBinding xmlns=”urn:schemas-microsoft-com:asm.v1″> <probing privatePath=”c:SharedObjectsDebug”/>
</assemblyBinding>
</runtime>
</conmfiguration>
E.
The following code should be added to the machine configuration file:
<configuration>
<runtime>
<assemblyBinding xmlns=”urn:schemas-microsoft-com:asm.v1″> <dependantAssembly>
<assemblyIdentity name=”BillSharedObjects” publicKeyToken=”12ac3ab67e0a34b5″culture=”en-us”/>
<codeBase version=”2.0.0.0″ href=”BillSharedObjectsDebug”/>
</dependantAssembly>
</assemblyBinding>
</runtime>
</configuration>
F.
The following code should be added to the machine configuration file:
<configuration>
<runtime>
<developmentMode developerInstallation=”true”/>
</runtime>
</configuration>