search

avogelba / WinDirStats

WinDirStats - Windows Directory Statistics, private clone from:
https://bitbucket.org/windirstat/windirstat
GNU General Public License v2.0
5 stars 0 forks source link

Create a WiX project for WDS and author the setup #28

Open avogelba opened 11 years ago

avogelba commented 11 years ago

Originally reported by: Oliver (Bitbucket: assarbad, GitHub: assarbad)

We need to create two MSI packages that behave nicely for network admins and install the 64 and 32 bit versions respectively, i.e. one package per bitness (only x64 and x86, not IA-64).

Those MSIs should be localized in the respective supported languages and should be controllable by setting respective properties on the command line (to override/manipulate) behavior. This will allow us to use a small NSIS wrapper, aside from the MSI packages which can be offered on their own as downloads, to offer a one--in-all installer for the end user.

Assigning to you, Finnbogi. Let's figure out the details together in here. Including the version of WiX to use and so on :)

avogelba commented 10 years ago

Original comment by Oliver (Bitbucket: assarbad, GitHub: assarbad):

So Finnbogi sent me a draft version of the WiX installer project. Thanks.

avogelba commented 10 years ago

Original comment by Oliver (Bitbucket: assarbad, GitHub: assarbad):

Command line is the preferred method and it's fine to put the project into a VS 2013 solution. We can talk over the layout here or using Jabber ;) btw: I don't find it too bad if NSIS is required.

avogelba commented 10 years ago

Original comment by Finnbogi Finnbogason (Bitbucket: frammi, GitHub: Unknown):

Sorry for the extremely long absence.

I am still interested in putting this together. Oliver assigned to me at first because I had worked out a rather clever setup of one/more native MSIs (minimal use of customactions) chained together and providing multilingual setup UI using NSIS.

As I'm not sure what the preferred VS version would be, I will keep with building from command line and provide a batch for the process.

I may be able to dig out preferences in discussions elsewhere in the project, but I would appreciate if there are any special wishes for better conform with the overall project.

I do like the idea of using the Burn bootstrapper. However I haven't done much with it since at the time I was working with WiX the most the Burn engine was pretty much in beta. I will look into it though, but it would need to be able to replace the need for NSIS entirely...

avogelba commented 10 years ago

Original comment by Oliver (Bitbucket: assarbad, GitHub: assarbad):

Yes. I have spent weeks now moving from one country to another, so all else was on ice.

avogelba commented 10 years ago

Original comment by Tim Rozetar (Bitbucket: timrozetar, GitHub: Unknown):

Is this still in progress?

avogelba commented 10 years ago

Original comment by Alasdair King (Bitbucket: alasdairking, GitHub: alasdairking):

I'd be happy to do simple WiX-based MSI Windows Installer files for WDS and return the WiX code if that's any help to get started.

avogelba commented 10 years ago

Original comment by Anonymous:

Since you're going to author the MSIs using WiX, I'd recommend creating the .exe using WiX too: http://wixtoolset.org/documentation/manual/v3/bundle/ .

The 'Burn' bootstrapper is used by Visual Studio, WDK, SDK etc.

avogelba commented 10 years ago

Original comment by Oliver (Bitbucket: assarbad, GitHub: assarbad):

Related to Issue #82