which requires complex installation logic to create a custom installer for the business application?

You have recently created a business application, which requires complex installation logic.
You add the following code to your project after electing to create a custom installer for the business application.
public class ApplicationInstaller : Installer {
public override void Install (IDictionary stateSaver) {
//Install the application
Base.Install (stateSaver);
}
public override void Commit (IDictionary savedState) {
//Commit the application

You have recently created a business application, which requires complex installation logic.
You add the following code to your project after electing to create a custom installer for the business application.
public class ApplicationInstaller : Installer {
public override void Install (IDictionary stateSaver) {
//Install the application
Base.Install (stateSaver);
}
public override void Commit (IDictionary savedState) {
//Commit the application

A.
The assembly should be compiled and the Install.exe tool should be run.

B.
The RunInstaller attribute should be added to the business application assembly and it should be set to true.

C.
The assembly should be compiled and should be run as normal.

D.
The RunInstaller attribute should be added to the ApplicationInstaller class and it should be set to true.

Explanation:

Incorrect Answers:
A: This option should be executed after applying the RunInstaller attribute and setting it to true.
B: You should not add the RunInstaller attribute to the assembly because the RunInstaller attribute is applied to a class, not the entire assembly.
C: You should not use this option because the installer class will be invoked without applying the RunInstaller attribute with a value of true.



Leave a Reply 1

Your email address will not be published. Required fields are marked *


networkmanagers

networkmanagers

I have the same idea.