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 69093
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 10, 20262026-05-10T19:31:10+00:00 2026-05-10T19:31:10+00:00

The installer sets up a default DB (if one doesn’t already exist) and I

  • 0

The installer sets up a default DB (if one doesn’t already exist) and I want to exclude that from the uninstall process (Or have the user option to remove it or not, once I take the time to figure out customizing the GUI)

Seems like best practice would be to just create the DB at runtime rather than install time, but for the sake of argument, is this possible and how?

I know how to set it up to install it conditionally like this:

<Feature Id='Database' Display='hidden' Level='1'>   <ComponentRef Id='DatabaseComponent'/>   <!-- Cancels installing of new DB if it already exists-->   <Condition Level='0'>DBEXISTS</Condition> </Feature> 

But I’m not sure about how to put a conditional on an uninstall.

  • 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. 2026-05-10T19:31:10+00:00Added an answer on May 10, 2026 at 7:31 pm

    Make the Component permanent (Component@Permanent=’yes’).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a custom installer action that updates the PATH environment, and creates an
I have a WSI installer package that I'm using to install my application. The
We have an MSI installer for a .Net WinForms app for Windows XP that
I'm creating an installer for a website that uses a custom event log source.
Our installer is written with Inno Setup and we are actually quite happy with
I'm building an installer for an application. The user gets to select a datasource
I'm building an installer for an application. The user gets to select a datasource
I am creating an installer for an ASP.Net website using WiX. How do you
I am creating a installer in .NET and using custom actions for controlling installation.

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.