[WiX-users] create a bootstrap that passes arguments to the msiexec
I need to create a bootstrap for my WiX project I've tried using * setupbld.exe* but it will only allow me to create an executable that will show my UI or one that will behave as a silent installer but not both. I need to be able to run the resulting executable with argument that will tell it wether or not to show the UI during installation. I've found this post by John Robbinshttp://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-a-bootstrap-loader-with-wix-3-0.aspx that explains how to re-build the setup.exe stub used in the creation of the bootstrap but I was hoping there is a simpler way to do what I need. Does anyone know of a way to create a bootstrap that I use to run either as a simple (with UI) install or as a silent install. Dror Helper [image: Helper Code] http://feeds.feedburner.com/~r/HelperCode/~6/2 -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.5 Source Code
I agree that the bug-tracking/discussion system of Codeplex needs improvement. Why not keeping the bug-tracking and mailing lists (except the commit-list) on sf? It's free :-) and working fine... Regards Stephen -- Stephen Reindl CTO Tideum Deutschland AG Justus-Liebig-Straße 3 D-41564 Kaarst Tel.: +49 (0)2131 - 153056 - 0 Fax: +49 (0)2131 - 153056 - 11 Mobil: +49 (0)15 1 - 54 77 27 63 stephen.rei...@tideum.com www.tideum.com The information transmitted is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Company information: Sitz der Gesellschaft: Kaarst - Registergericht Neuss HRB 14784 - Vorstand: Andreas Hackethal, Stephen Reindl Aufsichtsrat: Andreas Jaeger (Vorsitzender), Dr. Carsten S. Wehn, Georg Wolter Freiherr von Stackelberg -Ursprüngliche Nachricht- Von: Rob Mensching [mailto:r...@robmensching.com] Gesendet: Sonntag, 25. April 2010 07:27 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] WiX 3.5 Source Code Fair enough. I guess I took silence as a lack of interest and didn't appropriately weight the fact that slow updates to CVS would prevent interest (yes, sometimes I'm slow smile/). I have been investigating CodePlex ever since they added Mercurial support. Given the number of comments here about the preference for CodePlex, I give it decent odds we'll move there. I still dislike the discussion system (why can't they just have a real mailing list?) and the bug tracker isn't really any better than SourceForge. Anyway, as I've mentioned to some, I've been a bit over capacity for the last few months. Things will be improving through May. Lots of churn right now... thanks for the feedback here. On Sat, Apr 24, 2010 at 8:31 PM, John H. Bergman (XPedient Technologies) john.berg...@xpedienttechnologies.com wrote: I agree with that, if it were on codeplex, I would probably be more apt to dig through the source myself to work through some of the things that give me fits. -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Saturday, April 24, 2010 5:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.5 Source Code I would like to see it on Codeplex like other Microsoft projects. Neil -Original Message- From: Dieter Lunn [mailto:coder2...@gmail.com] Sent: 24 April 2010 23:43 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.5 Source Code Has there been any discussion of moving to a different VCS like SVN, Git or Mercurial? Dieter Lunn http://www.coder2000.ca On Sat, Apr 24, 2010 at 5:06 PM, Rob Mensching r...@robmensching.com wrote: Stephen, Sorry, the lack of CVS updates is my fault. CVS has been giving me fits lately and I have not been prioritizing getting to the root of the issues because I didn't think anyone really cared. Neil is one of about three people that have *ever* asked about CVS and I don't think he hasn't asked about it since we got the WiX v3.0 issues worked out. smile/ I am kicking CVS again right now. I'm still seeing intermittent issues but some things are at least moving along. Hopefully it'll all be updated in the next hour. Again, sorry for causing you stress. Neil, I thought we had the binary files all fixed. On Sat, Apr 24, 2010 at 12:06 PM, Stephen Reindl stephen.rei...@tideum.comwrote: ... 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
Re: [WiX-users] create a bootstrap that passes arguments to the msiexec
Check out http://dotnetinstaller.codeplex.com. It will do everything you need and more. dB. @ dblock.org Moscow|Geneva|Seattle|New York -Original Message- From: Dror Helper [mailto:dror.hel...@gmail.com] Sent: Sunday, April 25, 2010 4:40 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] create a bootstrap that passes arguments to the msiexec I need to create a bootstrap for my WiX project I've tried using * setupbld.exe* but it will only allow me to create an executable that will show my UI or one that will behave as a silent installer but not both. I need to be able to run the resulting executable with argument that will tell it wether or not to show the UI during installation. I've found this post by John Robbinshttp://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-a-bootstrap-loader-with-wix-3-0.aspx that explains how to re-build the setup.exe stub used in the creation of the bootstrap but I was hoping there is a simpler way to do what I need. Does anyone know of a way to create a bootstrap that I use to run either as a simple (with UI) install or as a silent install. Dror Helper [image: Helper Code] http://feeds.feedburner.com/~r/HelperCode/~6/2 -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.5 Source Code
I'd second that. -Original Message- From: Stephen Reindl [mailto:stephen.rei...@tideum.com] Sent: 25 April 2010 11:13 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.5 Source Code I agree that the bug-tracking/discussion system of Codeplex needs improvement. Why not keeping the bug-tracking and mailing lists (except the commit-list) on sf? It's free :-) and working fine... Regards Stephen -- Stephen Reindl CTO Tideum Deutschland AG Justus-Liebig-Straße 3 D-41564 Kaarst Tel.: +49 (0)2131 - 153056 - 0 Fax: +49 (0)2131 - 153056 - 11 Mobil: +49 (0)15 1 - 54 77 27 63 stephen.rei...@tideum.com www.tideum.com The information transmitted is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Company information: Sitz der Gesellschaft: Kaarst - Registergericht Neuss HRB 14784 - Vorstand: Andreas Hackethal, Stephen Reindl Aufsichtsrat: Andreas Jaeger (Vorsitzender), Dr. Carsten S. Wehn, Georg Wolter Freiherr von Stackelberg -Ursprüngliche Nachricht- Von: Rob Mensching [mailto:r...@robmensching.com] Gesendet: Sonntag, 25. April 2010 07:27 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] WiX 3.5 Source Code Fair enough. I guess I took silence as a lack of interest and didn't appropriately weight the fact that slow updates to CVS would prevent interest (yes, sometimes I'm slow smile/). I have been investigating CodePlex ever since they added Mercurial support. Given the number of comments here about the preference for CodePlex, I give it decent odds we'll move there. I still dislike the discussion system (why can't they just have a real mailing list?) and the bug tracker isn't really any better than SourceForge. Anyway, as I've mentioned to some, I've been a bit over capacity for the last few months. Things will be improving through May. Lots of churn right now... thanks for the feedback here. On Sat, Apr 24, 2010 at 8:31 PM, John H. Bergman (XPedient Technologies) john.berg...@xpedienttechnologies.com wrote: I agree with that, if it were on codeplex, I would probably be more apt to dig through the source myself to work through some of the things that give me fits. -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Saturday, April 24, 2010 5:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.5 Source Code I would like to see it on Codeplex like other Microsoft projects. Neil -Original Message- From: Dieter Lunn [mailto:coder2...@gmail.com] Sent: 24 April 2010 23:43 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.5 Source Code Has there been any discussion of moving to a different VCS like SVN, Git or Mercurial? Dieter Lunn http://www.coder2000.ca On Sat, Apr 24, 2010 at 5:06 PM, Rob Mensching r...@robmensching.com wrote: Stephen, Sorry, the lack of CVS updates is my fault. CVS has been giving me fits lately and I have not been prioritizing getting to the root of the issues because I didn't think anyone really cared. Neil is one of about three people that have *ever* asked about CVS and I don't think he hasn't asked about it since we got the WiX v3.0 issues worked out. smile/ I am kicking CVS again right now. I'm still seeing intermittent issues but some things are at least moving along. Hopefully it'll all be updated in the next hour. Again, sorry for causing you stress. Neil, I thought we had the binary files all fixed. On Sat, Apr 24, 2010 at 12:06 PM, Stephen Reindl stephen.rei...@tideum.comwrote: ... 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
Re: [WiX-users] WiX 3.5 Source Code
Rob, could I suggest that as a first step we (I don't mind helping if that helps) get the source zip file working? At the moment it is not complete and that is why I use CVS. Also, as of 3.5.1623.0 it fails to build due to missing/incorrect files. Neil -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 25 April 2010 06:27 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.5 Source Code Fair enough. I guess I took silence as a lack of interest and didn't appropriately weight the fact that slow updates to CVS would prevent interest (yes, sometimes I'm slow smile/). I have been investigating CodePlex ever since they added Mercurial support. Given the number of comments here about the preference for CodePlex, I give it decent odds we'll move there. I still dislike the discussion system (why can't they just have a real mailing list?) and the bug tracker isn't really any better than SourceForge. Anyway, as I've mentioned to some, I've been a bit over capacity for the last few months. Things will be improving through May. Lots of churn right now... thanks for the feedback here. On Sat, Apr 24, 2010 at 8:31 PM, John H. Bergman (XPedient Technologies) john.berg...@xpedienttechnologies.com wrote: I agree with that, if it were on codeplex, I would probably be more apt to dig through the source myself to work through some of the things that give me fits. -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Saturday, April 24, 2010 5:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.5 Source Code I would like to see it on Codeplex like other Microsoft projects. Neil -Original Message- From: Dieter Lunn [mailto:coder2...@gmail.com] Sent: 24 April 2010 23:43 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.5 Source Code Has there been any discussion of moving to a different VCS like SVN, Git or Mercurial? Dieter Lunn http://www.coder2000.ca On Sat, Apr 24, 2010 at 5:06 PM, Rob Mensching r...@robmensching.com wrote: Stephen, Sorry, the lack of CVS updates is my fault. CVS has been giving me fits lately and I have not been prioritizing getting to the root of the issues because I didn't think anyone really cared. Neil is one of about three people that have *ever* asked about CVS and I don't think he hasn't asked about it since we got the WiX v3.0 issues worked out. smile/ I am kicking CVS again right now. I'm still seeing intermittent issues but some things are at least moving along. Hopefully it'll all be updated in the next hour. Again, sorry for causing you stress. Neil, I thought we had the binary files all fixed. On Sat, Apr 24, 2010 at 12:06 PM, Stephen Reindl stephen.rei...@tideum.comwrote: ... 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
Re: [WiX-users] Speeding up Light command
On 4/22/2010 12:45 PM, Pally Sandher wrote: If only I could get the same sort of improvements out of msimsp.exe too They don't have multiple cabs, so the same approach doesn't work. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] illegal MsiFileHash entries
On 4/23/2010 6:24 PM, Alan Sinclair wrote: File Id=lwf.cat CompanionFile=lwf.inf Name=lwf.cat Vital=yes Source=Z:\sdk\install\lwf.cat / Can you file a bug? Companion files should be versioned files; ICE60 implies they must be. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] PropertyRef WIX_SUITE_WH_SERVER
Check a verbose log for the WixQueryOsInfo custom action. On 4/22/2010 6:34 PM, gapearce wrote: Bump? -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.5 Source Code
On 4/25/2010 8:26 AM, Neil Sleightholm wrote: Rob, could I suggest that as a first step we (I don't mind helping if that helps) get the source zip file working? At the moment it is not complete and that is why I use CVS. Also, as of 3.5.1623.0 it fails to build due to missing/incorrect files. Which? We still have the limited-space issue, which is why we intentionally exclude large binaries, which are available both in CVS and from the binaries .zip. If there are other source files missing, that's a bug. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: Add attribute Win64=yes to Component elements?
On 4/22/2010 7:29 PM, Sascha Beaumont wrote: No, heat doesn't harvest 64-bit information. I just do a find/replace (sed would work from the command line if it needs scripting) Find: Guid=* Replace: Guid=* Win64=yes If you use the -arch switch, Candle will do that for you. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Light performance with cabinets and merge modules
On 4/21/2010 8:41 PM, Nick K wrote: If I create merge modules, and then place each merge module into its own .cab (for the final .msi), will that tell light not to un-pack and re-pack all the files? No. Merge modules have their own embedded .cabs but their files need to be sequenced based on how their components are merged in. Or, alternately, will I see more performance improvement if I assign a RAMdisk or similar? Sure. Binding takes two kinds of resources: i/o, to collect the files and write them out; and CPU, if you compress the .cabs. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Change Existing Service User Account
On 4/21/2010 7:08 AM, stevenjly...@hbosplc.com wrote: Will ServiceInstall 'update' an existing service? Probably, but note that it will also uninstall the service when the product is uninstalled. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How do you extract COM registration info from a 64-bit DLL or TLB?
On 4/22/2010 1:08 PM, Younie, Bradford wrote: Now, I need to produce a 64-bit version of the same product, but I build it all on a 32-bit computer. When heat tries to harvest the data from the 64-bit DLL and TLB, it fails. I understand why it fails: it can't load the 64-bit DLL on a 32-bit system. But is there a way around it? Don't harvest the 64-bit component; harvest the 32-bit and use the same authoring compiled for 64-bit. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What does Light do?
On 4/22/2010 1:57 PM, Nick Ramirez wrote: We'd like to optimize our calls to Light and any info about the order of things would really help. It would also be implementation-dependent and likely to change. What are you looking to optimize? -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.5 Source Code
Stephen, you are walking my thinking. smile/ The question I asked Sara before realizing she was gone was, Can I turn off the Issue Tracker on CodePlex? I want to avoid confusion about where to file bugs if at all possible. I know it is possible to turn off the Discussions tab so we would get people asking questions where no one is looking. It's coming together... just all at the same time as everything else. sigh/ -- virtually, Rob Mensching - http://RobMensching.com LLC On Sun, Apr 25, 2010 at 3:13 AM, Stephen Reindl stephen.rei...@tideum.comwrote: I agree that the bug-tracking/discussion system of Codeplex needs improvement. Why not keeping the bug-tracking and mailing lists (except the commit-list) on sf? It's free :-) and working fine... Regards Stephen -- Stephen Reindl CTO Tideum Deutschland AG Justus-Liebig-Straße 3 D-41564 Kaarst Tel.: +49 (0)2131 - 153056 - 0 Fax: +49 (0)2131 - 153056 - 11 Mobil: +49 (0)15 1 - 54 77 27 63 stephen.rei...@tideum.com www.tideum.com The information transmitted is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Company information: Sitz der Gesellschaft: Kaarst - Registergericht Neuss HRB 14784 - Vorstand: Andreas Hackethal, Stephen Reindl Aufsichtsrat: Andreas Jaeger (Vorsitzender), Dr. Carsten S. Wehn, Georg Wolter Freiherr von Stackelberg -Ursprüngliche Nachricht- Von: Rob Mensching [mailto:r...@robmensching.com] Gesendet: Sonntag, 25. April 2010 07:27 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] WiX 3.5 Source Code Fair enough. I guess I took silence as a lack of interest and didn't appropriately weight the fact that slow updates to CVS would prevent interest (yes, sometimes I'm slow smile/). I have been investigating CodePlex ever since they added Mercurial support. Given the number of comments here about the preference for CodePlex, I give it decent odds we'll move there. I still dislike the discussion system (why can't they just have a real mailing list?) and the bug tracker isn't really any better than SourceForge. Anyway, as I've mentioned to some, I've been a bit over capacity for the last few months. Things will be improving through May. Lots of churn right now... thanks for the feedback here. On Sat, Apr 24, 2010 at 8:31 PM, John H. Bergman (XPedient Technologies) john.berg...@xpedienttechnologies.com wrote: I agree with that, if it were on codeplex, I would probably be more apt to dig through the source myself to work through some of the things that give me fits. -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Saturday, April 24, 2010 5:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.5 Source Code I would like to see it on Codeplex like other Microsoft projects. Neil -Original Message- From: Dieter Lunn [mailto:coder2...@gmail.com] Sent: 24 April 2010 23:43 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.5 Source Code Has there been any discussion of moving to a different VCS like SVN, Git or Mercurial? Dieter Lunn http://www.coder2000.ca On Sat, Apr 24, 2010 at 5:06 PM, Rob Mensching r...@robmensching.com wrote: Stephen, Sorry, the lack of CVS updates is my fault. CVS has been giving me fits lately and I have not been prioritizing getting to the root of the issues because I didn't think anyone really cared. Neil is one of about three people that have *ever* asked about CVS and I don't think he hasn't asked about it since we got the WiX v3.0 issues worked out. smile/ I am kicking CVS again right now. I'm still seeing intermittent issues but some things are at least moving along. Hopefully it'll all be updated in the next hour. Again, sorry for causing you stress. Neil, I thought we had the binary files all fixed. On Sat, Apr 24, 2010 at 12:06 PM, Stephen Reindl stephen.rei...@tideum.comwrote: ... 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
Re: [WiX-users] WiX 3.5 Source Code
The details are here http://neilsleightholm.blogspot.com/2008/10/how-to-create-wix-build-mach ine.html, they are all broken in CVS for 3.5 and not in the binaries zip at all. If space is the issue then either CVS needs to be fixed or the files should be available for download in another form. I have raised this as a bug before but the interest in fixing it seems to be limited. I realise I am in a minority of people that want to build the WiX source but it does suffer from works on my machine. Neil -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: 25 April 2010 14:31 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX 3.5 Source Code On 4/25/2010 8:26 AM, Neil Sleightholm wrote: Rob, could I suggest that as a first step we (I don't mind helping if that helps) get the source zip file working? At the moment it is not complete and that is why I use CVS. Also, as of 3.5.1623.0 it fails to build due to missing/incorrect files. Which? We still have the limited-space issue, which is why we intentionally exclude large binaries, which are available both in CVS and from the binaries .zip. If there are other source files missing, that's a bug. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] PropertyRef WIX_SUITE_WH_SERVER
Thanks for the hint, Bob. I ran the installer and produced a log, but I don't see anything obviously wrong in there. (But I'm a noob). I ran this on a WH Server, using V3.0.5419 of WiX, and it prevents me from installing. Maybe you could take a quick look? I'd appreciate it... I included this log file: http://n2.nabble.com/forum/FileDownload.jtp?type=nid=4960181name=logname.log logname.log Here's the relevant snip: MSI (c) (80:D4) [18:17:43:044]: Doing action: WixQueryOsInfo MSI (c) (80:D4) [18:17:43:044]: Note: 1: 2205 2: 3: ActionText Action 18:17:43: WixQueryOsInfo. Action start 18:17:43: WixQueryOsInfo. MSI (c) (80:1C) [18:17:43:059]: Invoking remote custom action. DLL: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\MSI13.tmp, Entrypoint: WixQueryOsInfo MSI (c) (80:6C) [18:17:43:075]: Cloaking enabled. MSI (c) (80:6C) [18:17:43:075]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (80:6C) [18:17:43:075]: Connected to service for CA interface. Action ended 18:17:43: WixQueryOsInfo. Return value 1. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-PropertyRef-WIX-SUITE-WH-SERVER-tp4958608p4960181.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
