You work as the application developer at Domain.com.
Domain.com uses Visual Studio.NET 2005 as its application development platform.
You are developing a .NET Framework 2.0 Windows application that will make use of an assembly named BillAssembly.
The assembly file BillAssembly.dll is deployed in a folder named Test20 under the application root directory.
The BillAssembly assembly was not strongly named

You are required to configure the Windows application to specify the location of the BillAssembly assembly whilst any settings that you change not affect other applications installed on the system.
What should you do?

A.
The application configuration file must be modified to add the following setting to the <assemblyBinding> section:
<probing privatePath=”Test20BillAssembly.dll”/>

B.
The machine configuration file should be modified to add the following setting to the <assemblyBinding> section:
<codeBase href=”Test20″/>

C.
The machine configuration file must be modified to add the following setting to the <assemblyBinding> section for the BillAssembly assembly:
<codeBase href=”Test20/BillAssembly.dll”/>

D.
The application configuration file should be modified to add the following section to the <assemblyBinding> section:
<probing privatePath=”Test20″/>

Explanation:

Since the BillAssembly assembly is not strongly named the configuration will have to be made at the local level by making use of the application configuration files as is the case in the scenario.
Incorrect Answers:
A, B: The modification of the machine configuration file is incorrect as the assembly in