I revised our windows installer for the upcoming release. The most important change are:
- The installer wizard only shows two pages: One for the directory to install to, and one during the unpacking of the files
- Users without admin rights can run the installer and the default target directory is chosen appropriately
- The target directory defaults to the directory of a previous installation
- The rules to create the installer are now in CMakeLists.txt, so anyone who can compile OpenClonk for Windows can install NSIS and build the installer
Now I only need to find somewhere to upload a snapshot for testing.
- The installer wizard only shows two pages: One for the directory to install to, and one during the unpacking of the files
- Users without admin rights can run the installer and the default target directory is chosen appropriately
- The target directory defaults to the directory of a previous installation
- The rules to create the installer are now in CMakeLists.txt, so anyone who can compile OpenClonk for Windows can install NSIS and build the installer
Now I only need to find somewhere to upload a snapshot for testing.
> - Users without admin rights can run the installer and the default target directory is chosen appropriately
On Windows Vista/7, the user is asked for the administrator rights if the action he wants to take happens to require admin privileges. Is this case covered as well?
Well, I simply used the "MultiUser" script for NSIS, with "ExecutionLevel" "Highest". I would assume that vista and newer only ask for admin rights with that UAC thingy if the user is flagged as having them. If it always asks for a password for an admin account, that would be no worse than the previous situation, and the installer would at least do the right thing with a windows xp guest account. We probably could set the "ExecutionLevel" to "Standard" and make the user manually execute the installer with admin rights in order to install for all users. But I've been led to believe that vista and 7 users expect installers to ask for admin rights, and we wouldn't want to violate the users expectations, would we? ;-)
Yes, that is exactly what I meant: It should always ask for the admin privilegues.
>- Users without admin rights can run the installer and the default target directory is chosen appropriately
What happens if you install Win 64-Bit over 32-Bit or vice versa? Does it default to the corresponding program files instead of the previous install?
I apparently like to write stuff in obscure and arguably bad languages. XSLT, autotools, cmake, nsis, COM, ...
This time around, I made the installer put stuff into the "Game Explorer" thingy Vista introduced, made it use separate uninstall entries for separate installation locations, and register the game with the firewall. The last patch requires compilation of an nsis plugin DLL, which currently lacks CMake support, and the Game Explorer integration writes stuff into the source directory, because I didn't feel like figuring out how to tell MSVC where to find the file.
This time around, I made the installer put stuff into the "Game Explorer" thingy Vista introduced, made it use separate uninstall entries for separate installation locations, and register the game with the firewall. The last patch requires compilation of an nsis plugin DLL, which currently lacks CMake support, and the Game Explorer integration writes stuff into the source directory, because I didn't feel like figuring out how to tell MSVC where to find the file.
Attachment: 0006-win32-register-with-the-Game-Explorer.patch (15k)
Attachment: 0007-win32-Fill-in-Games-Explorer-XML-data-from-Version.t.patch (4k)
Attachment: 0008-win32-Installer-uses-a-per-installation-game-explore.patch (5k)
Attachment: 0009-win32-Every-install-location-gets-it-s-own-uninstall.patch (4k)
Attachment: 0010-win32-Add-a-firewall-exception-on-installation.patch (113k)
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill