Custom control packaging
Posted
by
CSharpened
on Stack Overflow
See other posts from Stack Overflow
or by CSharpened
Published on 2012-07-06T09:12:50Z
Indexed on
2012/07/06
9:15 UTC
Read the original article
Hit count: 221
homework
|custom-controls
Quick question:
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?
Package the control in a Merge Module (.msm) and add the .msm file to a Windows Installer project.
Package the control into a cabinet project (.cab) and add the .cab file to a Windows Installer project.
Create a separate directory for the control and then package it in a Windows Installer project along with the rest of the project files.
Package the control as a Web setup project and create a link to that project from the Windows Installer project.
Any ideas?
© Stack Overflow or respective owner