Skip to content

New Windows Installer #1401

Closed
Closed

Description

@karim

I opened this issue to track all the efforts to migrate our current NSIS installer to MSI (Windows Installer).

I'm not talking about changing CPack NSIS to CPack WIX, but using WiX Toolset instead to create the installer from scratch.

Migrating to Windows Installer will give us a greater control over the installation and will give the user the best possible experience. Also I saw it being requested a lot. Hopefully we can do it before our next big release.

I need to collect some information first to be able to create the new installer the way everyone wants.

Questions

  1. Do you want to install both 32-bit and 64-bit at the same time? Current installer requires removing one before installing the other.
  2. Do you want to install the stable version (for daily use) and the nightly version (to test new features/bug fixes) at the same time?
  3. Should all nightly builds be treated as the same product, that is, the new version replaces the old one, or should it be treated as a different product?
  4. Should we provide plugins as a different installer that can be installed later, or we bundle them together with DB4S? If bundled, should we allow the user to have the option to install them (Custom Install) or just install DB4S + Plugins (Full Install) automatically?

Instead of waiting I already answered these questions myself. 😄

Answers

  1. 32-bit and 64-bit are two different products and both can be installed together, even though I find it to be a useless option. It is only useful for 64-bit Windows and if you are on a 64-bit system why would you want to install 32-bit?
  2. Stable and Nightly are treated as the same product. If you have stable version installed and tried to install a nightly version it will upgrade the stable to nightly.
  3. All nightly are treated the same. Newer nightly version replaces the older one.
  4. Everything is installed by default. There is no option to install the application without the plugins or install the plugins separately.

Please feel free to comment if you didn't like any of these default settings so we can change them. I just made a PR (#1400) so we can test it and go from there.

Finally, all open issues related to this one should be closed and moved to here. Thank you! 😃

Activity

  1. self-assigned this
    on May 31, 2018
  2. chrisjlocke commented on May 31, 2018

    @chrisjlocke
    Member
    1. Not entirely sure this is a good idea? The nightly, while it has some updates and fixes, could introduce a nasty bug - not sure the user would appreciate blowing away their previous version? Guess its easy to redownload and reinstall again, but it could still be 'nasty'... ? Just a thought...
  3. justinclift commented on May 31, 2018

    @justinclift
    Member

    Good thinking. 😄

    It looks like we could add some suitable file extension associations to the installer too:

    My personal answers to the questions above are:

    1. For my use case (investigating reported problems) it'd be useful to install both 32-bit and 64-bit ones at the same time. That's not a "normal" use case though. 😉
    2. Being able to install both the stable (should be considered "known good") version + a nightly ("test out a new feature or fix") would be useful. But only if it's not confusing. If enabling this makes things potentially confusing for newbie users, I'd vote against it.
    3. No real preference. When debugging stuff it could be useful to have several nightlies installed in parallel somehow (maybe different dirs?). But it's not critical and not something I'd probably commonly use anyway.
    4. I'd just have everything in one installer, at least for now. I could see that if someone wants to make their own add-on modules/plugins (eg the GIS stuff) or something that places bits into an existing DB4S installation, that could be useful for people.
  4. justinclift commented on May 31, 2018

    @justinclift
    Member

    @remram44 Do you reckon this would be of interest to people in the various Carpentries projects?

    ie should someone jump on the new TopicBox server and point towards this discussion?

  5. justinclift commented on May 31, 2018

    @justinclift
    Member
  6. karim commented on May 31, 2018

    @karim
    MemberAuthor

    Not entirely sure this is a good idea? The nightly, while it has some updates and fixes, could introduce a nasty bug - not sure the user would appreciate blowing away their previous version?

    True. But my point was, if you are using the stable version, reported a bug, found it fixed in the nightly, downloaded and installed it, then it should upgrade your current stable version. Your current settings and file associations are the same and you can continue to use them without a problem. After all, our stable version is the latest nightly version at some point. 😃

    Users can also stop at a specific version and do not upgrade if they are satisfied with the version they have now, or can downgrade to an older nightly/stable.

    And later on, when we release a new stable version (with higher version than the latest nightly), they don't get stuck with a nightly version and get upgraded back to a stable version.

    And let's not forget that this way will make it possible to have four entries in Add/Remove Programs. 😄

    • DB Browser for SQLite (32-bit)
    • DB Browser for SQLite (32-bit) [Nightly]
    • DB Browser for SQLite (64-bit)
    • DB Browser for SQLite (64-bit) [Nightly]

    😱

  7. karim commented on May 31, 2018

    @karim
    MemberAuthor

    It looks like we could add some suitable file extension associations to the installer too

    Yeah. It is very powerful, but we should read the tutorial in order to get familiar with it.

    1. For my use case (investigating reported problems) it'd be useful to install both 32-bit and 64-bit ones at the same time. That's not a "normal" use case though.

    Personally, I don't like having 32-bit and 64-bit. It is good if you are using a portable version. You can run the 32-bit version if the system you are on is not 64-bit. But for an application you installed on your PC, why would you want to install a 32-bit version on a 64-bit PC? I don't find any use case for it.

    However, I made it possible that both versions can be installed.

  8. changed the title [-]Windows Installer[/-] [+]New Windows Installer[/+] on May 31, 2018
  9. karim commented on May 31, 2018

    @karim
    MemberAuthor
    1. No real preference. When debugging stuff it could be useful to have several nightlies installed in parallel somehow (maybe different dirs?). But it's not critical and not something I'd probably commonly use anyway.

    Well, this might not be as easy as it seems and deserves its own comment. 😃

    NSIS simply packs the files and throws them in a folder during installation. It is a simple extract + copy. It has no concept of versions. That made it possible to install multiple versions of the same application.

    If you install it in the same location it will overwrite the old one, effectively upgrading it. If it is installed in a different location it will be installed as new. But you only get one entry in "Add/Remove Programs" and pointing to the last installed version. Uninstalling the application from "Add/Remove Programs" will uninstall the last one only.

    MSI is different. It tracks each installed application by its GUID. Whenever you run a .msi file it will check this GUID. If the same GUID is found, it means the app is already installed, so it checks the version, if a higher version it will perform an upgrade, if lower version it will stop installing and say the app is installed with higher version already, if the same version it will show you the option to Repair/Configure it (add/remove features).

    So if you install a version in C:\This\Folder\ and then tried to install a different version of nightly in D:\Other\Folder\ the Windows Installer will detect that both are the same application, check the version, if the one you are installing now is higher it will upgrade the application by removing the first folder and installing the app in the second folder. Only one version will exist.

    As a workaround we can make each nightly build as a different product. This will make it possible to install each and every nightly version. We will lose the ability to upgrade though, since each version is a completely different product now.

    Whenever a user installs a new version of nightly to fix a bug or get a new feature, he/she will have to go to "Add/Remove Programs" and uninstall the older version also.

  10. justinclift commented on May 31, 2018

    @justinclift
    Member

    As a workaround we can make each nightly build as a different product. This will make it possible to install each and every nightly version. We will lose the ability to upgrade though, since each version is a completely different product now.

    Thanks Karim. For this, I'm thinking it's more important for people to be able to do upgrades easily, as that's (I think) by far the more common use case.

    So, lets go with the "same product" approach to enable easy upgrading. I can figure out some workaround for the occasional time I need to install things in parallel or test an older version of bits. 😄

  11. karim commented on May 31, 2018

    @karim
    MemberAuthor

    I can figure out some workaround for the occasional time I need to install things in parallel or test an older version of bits.

    Set AllowSameVersionUpgrades="no" attribute in MajorUpgrade element in product.wxs file then build the installer. Every new build will be a new product and can be installed with other builds built with this attribute set to "no". When you are done testing, set it back to "yes".

  12. justinclift commented on May 31, 2018

    @justinclift
    Member

    Thanks. 😄

  13. 4 remaining items

  14. JReally commented on Jun 1, 2018

    @JReally

    I can't say about the installer at the link you listed (I would assume it is the one)
    I just download Lazarus from this link http://www.lazarus-ide.org/
    and get the option in the screen shot.

  15. justinclift commented on Jun 1, 2018

    @justinclift
    Member

    Thanks @JReally. 😄

  16. MKleusberg commented on Jun 7, 2018

    @MKleusberg
    Member

    Just wondering, with the new Windows installer can we delete the cpack and/or NSIS bits at the end of the CMakeLists.txt file now or are they still needed? Same for the distri/winlaunch.bat file. 😄

  17. karim commented on Jun 7, 2018

    @karim
    MemberAuthor

    Just wondering, with the new Windows installer can we delete the cpack and/or NSIS bits at the end of the CMakeLists.txt file now or are they still needed? Same for the distri/winlaunch.bat file.

    Yes, we can delete them. At the moment, we are creating both, .exe. and .msi, till we find no problems with the new installer. We need to make sure also that the new installer can do everything the same as the old one.

  18. MKleusberg commented on Jun 7, 2018

    @MKleusberg
    Member

    Ah I see 😄 Thanks for the explanation!

  19. SilvioGrosso commented on Jun 10, 2018

    @SilvioGrosso

    Hello everyone,

    I am wondering whether, with this brand-new installer, it will be easier to package the "Math extension" [1] together with the upcoming next stable release ?
    From what I have gathered, with the previous installer available for Windows users, this extension was difficult to make it working correctly and thus not available to test so far.

    BTW, I suppose you are going to update your software with the Sqlite 3. 24.0 version [2] as well; but that's another different improvement, of course :-)

    THANKS a lot for your work on SqliteBrowser !

    [1] #1224
    [2] https://www.sqlite.org/releaselog/3_24_0.html

  20. justinclift commented on Jun 10, 2018

    @justinclift
    Member

    Oh, good point. I keep on forgetting about the Math extension. That shouldn't be too hard to include. 😄

    With SQLite 3.24.0, it's been in our nightly builds for a few days already. 😁

  21. SilvioGrosso commented on Jun 11, 2018

    @SilvioGrosso

    Thanks a lot for your reply.
    Just decided to sign up as a patreon for your project : you deserve it, really ! :-)

  22. justinclift commented on Jun 11, 2018

    @justinclift
    Member

    Wow! Thanks heaps @SilvioGrosso. That really does help. 👍

  23. justinclift commented on Jun 11, 2018

    @justinclift
    Member

    Heh Heh Heh

    With your becoming a Patron, we've just reached our first goal! Server costs look like they'll be covered now. Whoo! Hoooo! 😀

  24. justinclift commented on Jun 24, 2018

    @justinclift
    Member

    This SQLite extension looks like it would be useful:

        https://github.com/cldellow/sqlite-parquet-vtable

    A fairly in-depth blog post explaining what it does, and what it's useful for too:

    https://cldellow.com/2018/06/22/sqlite-parquet-vtable.html

    Seems like it would make things a lot easier for people using 1GB+ SQLite data sets.

  25. justinclift commented on Jun 24, 2018

    @justinclift
    Member

    Some useful follow up info on the sqlite-parquet-vtable extension:

        https://news.ycombinator.com/item?id=17387166

  26. karim commented on Jun 5, 2019

    @karim
    MemberAuthor

    Just got reminded by another issue that this one is still open. Sorry about that, closing now. 😄

  27. justinclift commented on Jun 6, 2019

    @justinclift
    Member

    It's all good. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions