The fire-wall exceptions work, but the device needs to be restarted. Is that worth it?
A more important problem is that windows overhauled the file associations a few years ago. The approach here doesn't work (but is at least consistent with how it worked before, so it might work for Windows < 10 or unupdated). The current go-to approach is the one used by firefox, and it happens after the installer, at first start-up of the program.
part of CURA-9157
- For enterprise versions all Cura-Enterprise versions older than 4.13 are removed.
- All Cura versions >= 4.13 are removed optionally with a setting in the custom dialog.
CURA-9157
This should ensure that updating a patch doesn't override
the uninstaller in the settings->Installed apps
Fixes: #13337
CURA-9670 Correct the version number in the uninstaller
This should ensure that each Cura version, either release, prerelease or development
Will be installed completely separate from earlier versions
Contributes to CURA-9459
This should ensure that the default directory will always falls back to
`"$PROGRAMFILES64\${APP_NAME}"` where `APP_NAME` is:
`{{ app_name }} {{ version_major }}.{{ version_minor }}.{{ version_patch }}.{{ version_build }}`
Contributes to CURA-9459
I believe this should ensure that specific
folders and location will then have a unique
path for this app in the registry, which
should make the install path version specific
Contributes to CURA-9365
Users other than the original installer, can't easily uninstall, even if they have the rights. This should be possible. Users without the rights can still try to start the program, but would then need permission and get kicked out. 'HKCU' is a shorthand referring _only_ to the current user. 'HKCR' is a shorthand that refers _both_ to the current user _and_ the local machine. Most (except one) of the registry keys in the old setup (with CPack) where 'installed' to the latter, only one, which doesn't even seem to exist anymore in the new setup, refrered to the former. In short: This commit should restore the ability to uninstall Cura from any sufficiently elevated account to do such action, as was done by the 'old' buildsystem.
should fixUltimaker/Cura#12582
