Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9015819
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 16, 20262026-06-16T03:50:42+00:00 2026-06-16T03:50:42+00:00

I have a software that assembled with about 19 different components. Right now I

  • 0

I have a software that assembled with about 19 different components. Right now I use 19 setup projects and 1 Winforms project that is the main installer. I want to move to WiX since I want to upgrade to visual studio 2012. My question is: is it possible to do that in WiX? In current setup I have, user able to decide which components to install by checking them out. Is it possible to create such experience with WiX? also is it possible in future to upgrade only one of those components?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-16T03:50:43+00:00Added an answer on June 16, 2026 at 3:50 am

    Yes, Wix it brilliant for this kind of thing, it calls them Features, you can simply setup a set of features (you can set the Level so that things you want installed by default (if you do) are checked, and things that are optional are unchecked (if you like). You can also have a feature under a feature, for children like:

    Product  
    -Feature 1  
    -Feature 2  
    --Feature 2 Documentation  
    --Feature 2 Admin Tools  
    -Feature 3 
    (etc)
    

    These support title/description etc to make it nice and user friendly.

    To setup the more advances UI features you will need to add a reference to the WixUIExtension.dll to the installer project, and add a UIRef element into the product (see this article) like:

    <UIRef Id="WixUI_FeatureTree" />
    

    You’ll probably want to setup a Feature for each of the “things” you want installed, then setup a ComponentGroup for each one, in that you can define any number of sub components that you want installed.

    Here’s a snippet that should do the above (note it’s not fully fleshed out, just an example):

    <UIRef Id="WixUI_FeatureTree" />
    
    <ComponentGroup Id="Component1">
      <ComponentRef Id="Component1"/>
    </ComponentGroup>
    
    <Component Id="Component1" Directory="directorytobeinstalledto">
      <File Id="File1" Source="fileweareinstalling"/>
    </Component>
    
    <Feature Id="Feature1" Title="Feature 1" Description="My Feature 1" Level="1">
      <ComponentGroupRef Id="Component1"/>
    </Feature>
    <Feature Id="Feature2" Title="Feature 2" Description="My Feature 2" Level="1">
      <Feature Id="Feature2.Docs" Title="Feature 2 Documentation" Description="My Feature 2 Documentation" Level="1000"/>
      <Feature Id="Feature2.Admin" Title="Feature 2 Admin Tools" Description="My Feature 2 Administration Tools" Level="1000"/>
    </Feature>
    <Feature Id="Feature3" Title="Feature 3" Description="My Feature 3" Level="0"/> <!-- disabled! -->
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We have this software that has a webservices component. Now, the administrator of this
I have this running software that is currently being used by about 400 people.
I have searched on the web for software that batch convert image at different
I have a list of requirements for a software project, assembled from the remains
We have software that runs fine under a normal Windows installation but when we
I have a software that is tracking an NTFS volume changes on a Windows
I have a software that runs on mac (using terminal program) the program is
I have a software renderer that I am porting from PC to the iPhone.
I have seen a lot of software that show that which registry has error.
What best practices have you used in unit testing embedded software that are peculiar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.