... fine, but as you've said, the blog entry is from 2008 and some of the software modules mentioned there is even no longer available (e.g. Sandbox help compiler 1.7)...
It's not the question on building extensions. I would like to apply some of the patches mentioned in SF bug tracking because waiting for someone to bring this into the sources doesn't fit into our development timeframe. We've more or less in RTM-Mode in one of our software products. One of the things that prevents us releasing the software is (besides some showstoppers on our side .-) bug #2990556. If we would have the ability to fix the problem (i.e. apply the patch) by ourselves, I wouldn't need to write mails longer than my arm :-(. I agree that as long as wix 3.5 is in beta I have to expect (and accept) bugs, wix 3.5 is the only platform that supports VSTS 2010 currently (the customer wanted to have the software developed with VSTS 2010 to get the chance to update to .NET 4.0 very soon). I personally do like the Idea of using wix because 1. It's free (and the site claims that source code is available) 2. It has a very valuable community (thanks folks for all the tips/blogs/questions/solutions available) 3. It can simply be stored in TFS besides the project (Votive is one of my personal favorites) What I would like to see from an open source solution is the chance to * fix bugs * enhance the software by myself * apply bugs fixed by the community and not applied until now in a given delivery and (if needed/possible) to pass the changes back to the community (we do this for other open source software that we use as well). I'm even willing to really spend some budget on things that need to be done. But this works only if there's a chance to 1. get access (at least reading) to a version control system that is up to date 2. get some documentation on how to build a development environment to develop and build wix that is now based on assumptions. Don't get me wrong: I do not want to start <blame> mode but currently I'm a little bit upset and we need to decide by end of next week if we stick on wix or if we need to switch to some other setup tool. Regards Stephen -----Ursprüngliche Nachricht----- Von: Neil Sleightholm [mailto:n...@x2systems.com] Gesendet: Samstag, 24. April 2010 10:18 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] WiX 3.5 Source Code I asked a similar question sometime ago and I believe the official source is held within Microsoft and then republished to CVS. The copy in CVS tends to lag behind the wix-sources.zip as republishing is manual. There are also issues with the CVS copy in that it has quite a lot of broken binary files. I have documented some of the things you need to do to build the source here: http://neilsleightholm.blogspot.com/2008/10/how-to-create-wix-build-mach ine.html. It focuses on WiX3 but I think it would apply to WiX3.5 (although the last time I tried a build of 3.5 it failed due to the binary issues in CVS and files missing from the zip). I would say that if you only want to rebuild extensions then the source is complete. Neil -----Original Message----- From: Stephen Reindl [mailto:stephen.rei...@tideum.com] Sent: 23 April 2010 16:08 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX 3.5 Source Code Hi all, We are using wix for development of setup tools for our software. As part of our efforts we would like to enhance Wix by some parts and (hopefully) share the results with you. In addition we are willing to provide some effort into fixing problems with Wix. The question is now: Where's the source code? With every weekly release you are providing wix-sources.zip which is more or less complete. ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
