G
Guest
Hi,
Does someone know the answer?
You are building a setup for your application. The application contains a
custom control developed by you, which will be shared across multiple
applications. How should you package the custom control?
A: Package the control in a Merge Module (.msm) and add the .msm file to a
Windows Installer project.
B: Package the control into a cabinet project (.cab) and add the .cab file
to a Windows Installer project.
C: Create a separate directory for the control and then package it in a
Windows Installer project along with the rest of the project files.
D: Package the control as a Web setup project and create a link to that
project from the Windows Installer project.
Thanks,
Monica
Does someone know the answer?
You are building a setup for your application. The application contains a
custom control developed by you, which will be shared across multiple
applications. How should you package the custom control?
A: Package the control in a Merge Module (.msm) and add the .msm file to a
Windows Installer project.
B: Package the control into a cabinet project (.cab) and add the .cab file
to a Windows Installer project.
C: Create a separate directory for the control and then package it in a
Windows Installer project along with the rest of the project files.
D: Package the control as a Web setup project and create a link to that
project from the Windows Installer project.
Thanks,
Monica