You have recently created and deployed an application using the .NET 1.1 CLR to all Domain.com users.
After a Domain.com administrator updates all user computers with the .NET 2.0 CLR, you run preliminary tests and find that the application you created using the .NET 1.1 CLR is not compatible with the .NET 2.0 CLR.
You need to ensure that the application can be run with the .NET 1.1 CLR.
What should you do?
A.
Use the following element in the application configuration file:
<configuration>
<startup>
<bindingRedirect oldVersion=”1.0.0.0″ newVersion=”1.1.0.0″ />
</startup>
</configuration>
B.
Use the following element in the application configuration file:
<configuration>
<startup>
<requiredRuntime version=”v1.1.4322″ safemode=”true” />
</startup>
</configuration>
C.
Use the following element in the application configuration file:
<configuration>
<startup>
<supportedRuntime version=”v1.1.4322″ />
<supportedRuntime version=”v1.0.3705″ />
</startup>
</configuration>
D.
Use the following element in the application configuration file:
<configuration>
<startup>
<unsupportedRuntime version=”v2.0.50727″ />
</startup>
</configuration>
Explanation:
This configuration element instructs the host system to launch the application using either
.NET 1.1 CLR or .NET 1.0 CLR rather than defaulting to the .NET 2.0 CLR. The supportedRuntime element identifies the versions of the CLR with which the application can be run.
The supportedRuntime element is only supported in assemblies built using.NET 1.1 or later.Incorrect Answers:
A: There is no such subelement as bindingRedirect that exists for the startup element.
B: The requiredRuntime element should only be used by assemblies built by using the .NET 1.0 Framework.
D: There is no such element as the unsupportedRuntime element that exists in the application configuration schema.