Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
So something is checking the platform setting on the dll ?, With VS2012 and VS2013, I'm getting problems if I start to set platform to anything else than anycpu on dll's now, what gives? On Fri, Nov 14, 2014 at 6:38 PM, Phil Wilson wrote: > To expand on what Rob said, it all just works. On an x64 system the > MSI service will be 64-bit. If you have a 32-bit CA you'll get a > 32-bit msiexec process launched to host it. If you have another CA > that requires impersonation, you'll see another msiexec process > running impersonated. The error you're seeing is nothing to do with > the with this architecture. It's just invalid for a 32-bit process to > access 64-bit modules. You are enumerating processes or you have a > process id that's 64-bit and you're using it from 32-bit code to > access the process? As Jacob says, if you're on a 64-bit system and > you want to do whatever you're doing, make a 64-bit version of your > Dll. > --- > Phil Wilson > > > On Fri, Nov 14, 2014 at 8:35 AM, John Cooper > wrote: > > That is the technique I use and it is necessary when access 64-bit-only > file system locations and the like. > > > > -- > > John Merryweather Cooper > > Senior Software Engineer | Enterprise Service Applications | Continuing > Development > > Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | > jocoo...@jackhenry.com > > > > > > > > -Original Message- > > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] > > Sent: Friday, November 14, 2014 10:32 AM > > To: General discussion about the WiX toolset. > > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe > for a 64-bit MsiPackage > > > > What is the bitness of your CA DLL? Just a stab in the dark but you > might need to have it compiled twice, once as 32 and once as 64, and have > the respective MSI package use the right CA DLL. > > > > > > -Original Message- > > From: Rob Mensching [mailto:r...@firegiant.com] > > Sent: Friday, November 14, 2014 9:53 AM > > To: General discussion about the WiX toolset. > > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe > for a 64-bit MsiPackage > > > > Custom actions are hosted by Windows Installer in a separate custom > action host process based on custom action type. > > > > _ > > Short replies here. Complete answers over there: > http://www.firegiant.com/ > > > > > > -Original Message- > > From: Ryan Waller [mailto:rwal...@microsoft.com] > > Sent: Friday, November 14, 2014 7:43 AM > > To: General discussion about the WiX toolset. > > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe > for a 64-bit MsiPackage > > > > Yes, Orca Summary shows it with Platform x64. > > > > > -- > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push notifications. > > Take corrective actions from your mobile device. > > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > -- > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push notifications. > > Take corrective actions from your mobile device. > > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > NOTICE: This electronic mail message and any files transmitted with it > are intended > > exclusively for the individual or entity to which it is addressed. The > message, > > together with any attachment, may contain confidential and/or privileged > information. > > Any unauthorized review, use, printing, saving, copying, disclosure or > distribution > > is strictly prohibited. If you have received this message in error, > please > > immediately advise the sender by reply email and delete all copies. > > > > > > > -- > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push notifications. > > Take corrective actions from your mobile device. > > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users >
Re: [WiX-users] Shared component between features
I did it like that earlier, no problems at all. On Tue, Nov 11, 2014 at 11:09 PM, pezmannen wrote: > Hi > > I have a product that consists of two features. Web and a Windows service. > They share some dll's that are gacced. Is it ok to inlude the > gac-components > in both features? They usually are installed together. It seems to work but > what is best practice? > > It now looks something like this > > > > > > > > > > > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Shared-component-between-features-tp7597857.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX v3.9 released
I versioncontrol all my files, but then again, I don't use visualstudio or some fancy tool for wix authoring, but beeing able to go back and see what changes one have done are invaluable. Git, subversion, and you will have control. On Mon, Nov 3, 2014 at 8:12 PM, Phill Hogland wrote: > I also congratulate everyone for the wix 3.9 release. > > In my decades of working with Installshield, it would create a backup of > the > project file, but more times than not also introduced breaking changes that > prevented my projects from compiling until I tracked down all of the > changes. > > In my work with wix from 3.7, 38, and 3.9 I have not experienced those > issues. Maybe it would be helpful to provide more details on what issues > you have encountered, including which version the project was at prior to > the update. > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-v3-9-released-tp7597644p7597690.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 > -- mvh Asbjørn -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to silently install embedded SQL
Isn't private deployment an option for this? http://erikej.blogspot.no/2011/02/using-sql-server-compact-40-with-wpf.html http://erikej.blogspot.no/2011/02/using-sql-server-compact-40-with.html On Mon, Nov 3, 2014 at 3:38 PM, Rainer Queck wrote: > Hi John > > thank you very much for your hints. > I tried "/quiet" only and but no success. > May be the missing flag to acknowledge the license is the problem. How > would I apply that? > > Thanks > Rainer > > Am 03.11.2014 15:24, schrieb John Cooper: > > 1) it is unusual to pass both /quiet and /passive -- the usual pattern > is /quiet (no UI) XOR /passive (progress dialog only); > > > > 2) I don't know about CE as I no longer use it, but for LocalDB or > SqlExpress there's a flag you have to set that takes the place of > acknowledging the license in the UI -- you may need that here; > > > > -- > > John Merryweather Cooper > > Senior Software Engineer | Enterprise Service Applications | Continuing > Development > > Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | > jocoo...@jackhenry.com > > > > > > > > -Original Message- > > From: Rainer Queck [mailto:rainer.qu...@qutronic.de] > > Sent: Monday, November 3, 2014 8:17 AM > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] How to silently install embedded SQL > > > > Hi > > > > I would like do do a unattended install of embedded sql server. > > Here is how I am doing it: > > > > > > > > > InstallCommand="/quiet /passive" > > RepairCommand="/quiet /passive" > > UninstallCommand="/uninstall /quiet /passive" > > > SourceFile="D:\Daten\Softwareentwicklung\Projekte\BfpNetR2\3_Entwicklung\Source\Main\3rdParty\Installs\SSCERuntime_x64-DEU.exe" > > InstallCondition="VersionNT64"/> > > > > > InstallCommand="/quiet /passive" > > RepairCommand="/quiet /passive" > > UninstallCommand="/uninstall /quiet /passive" > > > SourceFile="D:\Daten\Softwareentwicklung\Projekte\BfpNetR2\3_Entwicklung\Source\Main\3rdParty\Installs\SSCERuntime_x86-DEU.exe" > > InstallCondition="NOT VersionNT64"/> > > > > > > > > > > But the installation fails. The MSI Installer window pops up showing me > the possible option, among which I see "/quiet" and "/passive"... which I > am using. > > The Log contains: > > [073C:026C][2014-11-03T05:58:51]i301: Applying execute package: > > SSCERuntime_x86_DEU.exe, action: Install, path: C:\ProgramData\Package > Cache\EC420A4D2962E89796B7E7382BC0DCC944625052\SSCERuntime_x86-DEU.exe, > > arguments: '"C:\ProgramData\Package > > Cache\EC420A4D2962E89796B7E7382BC0DCC944625052\SSCERuntime_x86-DEU.exe" > > /quiet /passive' > > [073C:026C][2014-11-03T06:11:36]e000: Error 0x80070667: Process returned > > error: 0x667 > > [073C:026C][2014-11-03T06:11:36]e000: Error 0x80070667: Failed to > execute EXE package. > > [0F48:0D08][2014-11-03T06:11:36]e000: Error 0x80070667: Failed to > configure per-machine EXE package. > > [0F48:0D08][2014-11-03T06:11:36]i319: Applied execute package: > > SSCERuntime_x86_DEU.exe, result: 0x80070667, restart: None > > [0F48:0D08][2014-11-03T06:11:36]e000: Error 0x80070667: Failed to > execute EXE package. > > > > How can I get the SQLCE installed unattended? > > > > Thanks for help! > > > > Regards > > Rainer > > > > > -- > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > NOTICE: This electronic mail message and any files transmitted with it > are intended > > exclusively for the individual or entity to which it is addressed. The > message, > > together with any attachment, may contain confidential and/or privileged > information. > > Any unauthorized review, use, printing, saving, copying, disclosure or > distribution > > is strictly prohibited. If you have received this message in error, > please > > immediately advise the sender by reply email and delete all copies. > > > > > > > -- > > ___ > > 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 > -- mvh Asbjørn -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] perMachine optional shortcut creation...
What is the name of the alluser desktopfolder then?, when I do this, I wrap it into an directory-element, which contains an component, and then the shortcut, and the shortcut it self goes to the alluser desktop because perMachine is set. If the registryvalue which is required for removing it, is then pointing to the per-user desktopfolder, then something is not quite right so how is this solveable? On Fri, Oct 31, 2014 at 3:58 PM, Rob Mensching wrote: > DesktopFolder is a per-user location. > > _ > Short replies here. Complete answers over there: > http://www.firegiant.com/ > > > -Original Message- > From: Phill Hogland [mailto:phogl...@rimage.com] > Sent: Friday, October 31, 2014 7:53 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] perMachine optional shortcut creation... > > No. It smells wrong but that is what you need to do for a per-machine > installation. > > > -- > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] perMachine optional shortcut creation...
But for perMachine installation, isn't HKCU wrong?, it kinda works though. On Fri, Oct 31, 2014 at 3:37 PM, Phill Hogland wrote: > I use something like this (without the condition, but that could be added, > in > which case I would also make the component transitive): > > >Directory="MyMenuFolder" Name="Name" WorkingDirectory="DirId" > xmlns:wix="http://schemas.microsoft.com/wix/2006/wi"; /> >Name="myShortcut_someValue" Value="[ProductVersion]" Type="string" > KeyPath="yes" /> > > > > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/perMachine-optional-shortcut-creation-tp7597616p7597618.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 > -- mvh Asbjørn -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Automatically 'harvest' files in VS 2013
Are you thinking about the project output thingy with votive? http://wixtoolset.org/documentation/manual/v3/votive/votive_project_references.html On Thu, Oct 30, 2014 at 7:01 PM, Brian Enderle wrote: > I am referring to the task of harvesting files and creating a WXS file that > contains a list of the files to be installed. I don't have a problem with > doing the harvest as a BeforeBuild action but if there is an easier way I > would like to know how. > > Brian > > If you can't explain it simply, you don't understand it well enough. - > Albert Einstein > > On Thu, Oct 30, 2014 at 11:48 AM, John Cooper > wrote: > > > Possibly. I am referring to the Task to be clear. > > > > -- > > John Merryweather Cooper > > Senior Software Engineer | Enterprise Service Applications | Continuing > > Development > > Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | > > jocoo...@jackhenry.com > > > > > > > > -Original Message- > > From: Phill Hogland [mailto:phogl...@rimage.com] > > Sent: Thursday, October 30, 2014 10:43 AM > > To: wix-users@lists.sourceforge.net > > Subject: Re: [WiX-users] Automatically 'harvest' files in VS 2013 > > > > Is the discussion possibly confusing the use of the HarvestDirectory > > target (called in the Wix build process) and the HarvestDirectory task > > (which I also call from a custom target which the BeforeBuild target > > depends on, as some blogs suggest)? > > > > > > > > -- > > View this message in context: > > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Automatically-harvest-files-in-VS-2013-tp7597592p7597597.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 > > NOTICE: This electronic mail message and any files transmitted with it > are > > intended > > exclusively for the individual or entity to which it is addressed. The > > message, > > together with any attachment, may contain confidential and/or privileged > > information. > > Any unauthorized review, use, printing, saving, copying, disclosure or > > distribution > > is strictly prohibited. If you have received this message in error, > please > > immediately advise the sender by reply email and delete all copies. > > > > > > > > > -- > > ___ > > 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 > -- mvh Asbjørn -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?
ah, that worked fine like this: c b1 b2 b3 On Tue, Sep 16, 2014 at 7:45 PM, Rob Mensching wrote: > Ahh, I was probably looking at WiX v4.0 targets. > > At least you can control the prefix in WiX v3.x targets. > _ > Short replies here. Complete answers over there: > http://www.firegiant.com/ > > > -Original Message- > From: Asbjørn Mikkelsen [mailto:asbj...@neslekkim.net] > Sent: Tuesday, September 16, 2014 10:20 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] LGHT0284: Support for more than 260 characthers > in Path? > > In the wix2010.targets I found CleanFile defined, so I could remap one > file, but further on I found this: > > > File="$(IntermediateOutputPath)$(BindOutputsFilePrefix)%(CultureGroup.Identity)$(BindOutputsFileExtension)"> > > > > > Include="$(IntermediateOutputPath)$(BindContentsFilePrefix)%(CultureGroup.Identity)$(BindContentsFileExtension);$(IntermediateOutputPath)$(BindOutputsFilePrefix)%(CultureGroup.Identity)$(BindOutputsFileExtension);$(IntermediateOutputPath)$(BindBuiltOutputsFilePrefix)%(CultureGroup.Identity)$(BindBuiltOutputsFileExtension)"> > > > > > > > File="$(IntermediateOutputPath)$(BindContentsFilePrefix)%(CultureGroup.Identity)$(BindContentsFileExtension)"> > > > > > File="$(IntermediateOutputPath)$(BindBuiltOutputsFilePrefix)%(CultureGroup.Identity)$(BindBuiltOutputsFileExtension)"> > > > > So those seems to be built on the fly, instead of getting assigned to an > property as is done with CleanFile.. > > Same with the Light task inside there: > > > > BindContentsFile="$(IntermediateOutputPath)$(BindContentsFilePrefix)%(CultureGroup.Identity)$(BindContentsFileExtension)" > > > BindOutputsFile="$(IntermediateOutputPath)$(BindOutputsFilePrefix)%(CultureGroup.Identity)$(BindOutputsFileExtension)" > > > BindBuiltOutputsFile="$(IntermediateOutputPath)$(BindBuiltOutputsFilePrefix)%(CultureGroup.Identity)$(BindBuiltOutputsFileExtension)" > > > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce. > Perforce version control. Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?
In the wix2010.targets I found CleanFile defined, so I could remap one file, but further on I found this: So those seems to be built on the fly, instead of getting assigned to an property as is done with CleanFile.. Same with the Light task inside there: BindContentsFile="$(IntermediateOutputPath)$(BindContentsFilePrefix)%(CultureGroup.Identity)$(BindContentsFileExtension)" BindOutputsFile="$(IntermediateOutputPath)$(BindOutputsFilePrefix)%(CultureGroup.Identity)$(BindOutputsFileExtension)" BindBuiltOutputsFile="$(IntermediateOutputPath)$(BindBuiltOutputsFilePrefix)%(CultureGroup.Identity)$(BindBuiltOutputsFileExtension)" On Tue, Sep 16, 2014 at 6:41 PM, Asbjørn Mikkelsen wrote: > Hm, I added those in the same propertygroup as where OutputPath and > IntermediateOutputPath is set, but nothing happens, it generates stil the > same names > Where are those properties listed?, like what is avalable? > > In this doc: > http://wixtoolset.org/documentation/manual/v3/overview/light.html > I cant even find the parameter that is fed to light for these files even?, > like these parameters: > > -contentsfile obj\.wixproj.BindContentsFileListnb-NO.txt > -outputsfile obj\.wixproj.BindOutputsFileListnb-NO.txt > -builtoutputsfile > obj\.wixproj.BindBuiltOutputsFileListnb-NO.txt > > and in the msbuild log, that is the only place I see those names listed.. > > > > On Tue, Sep 16, 2014 at 6:00 PM, Rob Mensching wrote: > >> PS: I just remembered, you can change the name of those files in your >> .wixpproj by setting Properties like BindContentsFile, BindOutputsFile, etc. >> >> _ >> Short replies here. Complete answers over there: >> http://www.firegiant.com/ >> >> >> -Original Message- >> From: Rob Mensching [mailto:r...@firegiant.com] >> Sent: Monday, September 15, 2014 12:42 PM >> To: General discussion about the WiX toolset. >> Subject: Re: [WiX-users] LGHT0284: Support for more than 260 characthers >> in Path? >> >> We could make those binder data file paths shorter in WiX v4.0. >> >> _ >> Short replies here. Complete answers over there: >> http://www.firegiant.com/ >> >> -- >> Want excitement? >> Manually upgrade your production database. >> When you want reliability, choose Perforce. >> Perforce version control. Predictably reliable. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > > > -- > mvh > Asbjørn > -- mvh Asbjørn -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?
Hm, I added those in the same propertygroup as where OutputPath and IntermediateOutputPath is set, but nothing happens, it generates stil the same names Where are those properties listed?, like what is avalable? In this doc: http://wixtoolset.org/documentation/manual/v3/overview/light.html I cant even find the parameter that is fed to light for these files even?, like these parameters: -contentsfile obj\.wixproj.BindContentsFileListnb-NO.txt -outputsfile obj\.wixproj.BindOutputsFileListnb-NO.txt -builtoutputsfile obj\.wixproj.BindBuiltOutputsFileListnb-NO.txt and in the msbuild log, that is the only place I see those names listed.. On Tue, Sep 16, 2014 at 6:00 PM, Rob Mensching wrote: > PS: I just remembered, you can change the name of those files in your > .wixpproj by setting Properties like BindContentsFile, BindOutputsFile, etc. > > _ > Short replies here. Complete answers over there: > http://www.firegiant.com/ > > > -Original Message- > From: Rob Mensching [mailto:r...@firegiant.com] > Sent: Monday, September 15, 2014 12:42 PM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] LGHT0284: Support for more than 260 characthers > in Path? > > We could make those binder data file paths shorter in WiX v4.0. > > _ > Short replies here. Complete answers over there: > http://www.firegiant.com/ > > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce. > Perforce version control. Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?
As mentioned earlier, it's theintermediate files, in the obj\release folder files are names as ".txt" for instance In one project that gave me an filename for one of the files tha tis 76 characters long. Yes, the projectfilename with exension is 46 characters, but still, if these filenames could be shorter, it could be great, but I can see that these filenames are usefull for debugging etc The wixobj files in the same folder, they are on the other hand, short and nice. On Mon, Sep 15, 2014 at 6:28 PM, Rob Mensching wrote: > What sort of filenames are the issue? We may be able to generate them > differently depending on what they are. > > _ > Short replies here. Complete answers over there: > http://www.firegiant.com/ > > > > -Original Message- > From: Asbjørn Mikkelsen [mailto:asbj...@neslekkim.net] > Sent: Monday, September 15, 2014 8:52 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] LGHT0284: Support for more than 260 characthers > in Path? > > Jenkins, we have shortened several times now, also customize the wixproj > file so intermediate files are going to "obj" instead of "obj\Release", and > so on. > But it doesnt help that Wix creates those very long-named intermediate > files, 65 characters for one file, and we have already shortened the > projectname so far we can go. > > Is it possible to disable incremental linking/building on the > buildserver?, I guess it's there for speeding up when you compile several > times? > > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?
Jenkins, we have shortened several times now, also customize the wixproj file so intermediate files are going to "obj" instead of "obj\Release", and so on. But it doesnt help that Wix creates those very long-named intermediate files, 65 characters for one file, and we have already shortened the projectname so far we can go. Is it possible to disable incremental linking/building on the buildserver?, I guess it's there for speeding up when you compile several times? On Mon, Sep 15, 2014 at 5:41 PM, Tunney, Stephen wrote: > What are you using for a CI engine? Jenkins and CruiseControl.NET allow > for doing custom workspace roots that can help shorten your path lengths. > > Stephen Tunney > Nuance Communications, Inc. > Solutions Architect, Imaging Division > Waterloo, Ontario, Canada > stephen.tun...@nuance.com > 519-880-7463Office > NUANCE.COM > The experience speaks for itself ™ > > > -Original Message- > From: Asbjørn Mikkelsen [mailto:asbj...@neslekkim.net] > Sent: September-15-14 11:01 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] LGHT0284: Support for more than 260 characthers > in Path? > > So, if Windows Installer api does not support it, does that mean that > Light would not work? > > on the workstations where we develop and build, it works ok, but on the > buildserver, since it's scoping the output from versioncontrol for each > build, it crashes from time to time, very annoying, and this is 2014.. > > On Mon, Sep 15, 2014 at 4:43 PM, Rob Mensching wrote: > > > Win32 pretty consistently supports that syntax. .NET Framework pretty > > consistently does not. IIRC, Windows Installer API never supports it. > > IOW, we are mostly SOL. > > > > _ > > Short replies here. Complete answers over there: > > http://www.firegiant.com/ > > > > > > -Original Message- > > From: Tunney, Stephen [mailto:stephen.tun...@nuance.com] > > Sent: Monday, September 15, 2014 7:15 AM > > To: General discussion about the WiX toolset. > > Subject: Re: [WiX-users] LGHT0284: Support for more than 260 > > characthers in Path? > > > > Does prepending the path with " \\?\" help out at all? > > > > > > http://blogs.msdn.com/b/bclteam/archive/2007/02/13/long-paths-in-net-p > > art-1-of-3-kim-hamilton.aspx > > > > > > Stephen Tunney > > Nuance Communications, Inc. > > Solutions Architect, Imaging Division > > Waterloo, Ontario, Canada > > stephen.tun...@nuance.com > > 519-880-7463Office > > NUANCE.COM > > The experience speaks for itself (tm) > > > > > > -- > > > > Want excitement? > > Manually upgrade your production database. > > When you want reliability, choose Perforce Perforce version control. > > Predictably reliable. > > > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg. > > clktrk ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > -- > mvh > Asbjørn > > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce Perforce version control. > Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?
So, if Windows Installer api does not support it, does that mean that Light would not work? on the workstations where we develop and build, it works ok, but on the buildserver, since it's scoping the output from versioncontrol for each build, it crashes from time to time, very annoying, and this is 2014.. On Mon, Sep 15, 2014 at 4:43 PM, Rob Mensching wrote: > Win32 pretty consistently supports that syntax. .NET Framework pretty > consistently does not. IIRC, Windows Installer API never supports it. IOW, > we are mostly SOL. > > _ > Short replies here. Complete answers over there: > http://www.firegiant.com/ > > > -Original Message- > From: Tunney, Stephen [mailto:stephen.tun...@nuance.com] > Sent: Monday, September 15, 2014 7:15 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] LGHT0284: Support for more than 260 characthers > in Path? > > Does prepending the path with " \\?\" help out at all? > > > http://blogs.msdn.com/b/bclteam/archive/2007/02/13/long-paths-in-net-part-1-of-3-kim-hamilton.aspx > > > Stephen Tunney > Nuance Communications, Inc. > Solutions Architect, Imaging Division > Waterloo, Ontario, Canada > stephen.tun...@nuance.com > 519-880-7463Office > NUANCE.COM > The experience speaks for itself (tm) > > > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?
Visual Studio?, What have that to do with this? MSBuild is building the project, if MSBuild also have an issue, that's another thing, this is in the linking phase, not during authoring of the wixfiles.. And who is using visualstudio for authoring wix projects anyhow?, absolutely no help in using VS for that, notepad++ is way better (or any other editor for that matter.) On Mon, Sep 15, 2014 at 4:03 PM, Carter Young wrote: > The Visual Studio Limit is still 260. I don't think that Wix should > go greater than 260 when the IDE has issues... > > Carter > > Quoting neslekkim : > > > I thought Windows supports more than 260 characters by now? > > > > According to this: > > > http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath > > > > We run into path problems way to often with this.. > > > > > > > > -- > > View this message in context: > > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LGHT0284-Support-for-more-than-260-characthers-in-Path-tp7596814.html > > Sent from the wix-users mailing list archive at Nabble.com. > > > > > -- > > Want excitement? > > Manually upgrade your production database. > > When you want reliability, choose Perforce > > Perforce version control. Predictably reliable. > > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > > > > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multiple entries in ARP
ok, strange.. we change the last number on our bundles, but when installing new build over an exisiting, gives us two bundlesetupis in ARP.. Have been comparing other setups, also the wixbundle, but can't see what is different. There have been mentioned Bundle/RelatedBundle, but the wix-setup does not use that, so I'm not sure why this happens (using WixStdBa) On Thu, Sep 11, 2014 at 9:46 PM, Rob Mensching wrote: > Bundles use all four. No idea why Windows Installer chose to be different > with three. > > _ > Short replies here. Complete answers over there: > http://www.firegiant.com/ > > > > -Original Message- > From: neslekkim [mailto:asbj...@neslekkim.net] > Sent: Thursday, September 11, 2014 12:09 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Multiple entries in ARP > > Does it use 3 or 4 digits?, ie, 1.0.0 or 1.0.0.0 ? > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-entries-in-ARP-tp7579932p7596769.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce Perforce version control. > Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Cannot view RootView.xaml file in visual studio 2010
So what would be an good startingpoint?, since this is not very good documentet, some good startingpoints would be very nice.. As of now, wixba will be an starting point.. :) On Wed, Aug 27, 2014 at 5:07 PM, Rob Mensching wrote: > Sounds like you are getting snapshots of the source code from GitHub. > Usually, if you want the source code I'd say just use git to clone the repo. > > The WixBA also isn't designed to be a starting point. It's good as a > reference codebase but the source code certainly isn't packaged up as a > starter kit. > > ___ > FireGiant | Dedicated support for the WiX toolset | > http://www.firegiant.com/ > > -Original Message- > From: linos [mailto:lino...@hotmail.com] > Sent: Wednesday, August 27, 2014 5:49 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Cannot view RootView.xaml file in visual studio > 2010 > > Hi Rob, > > My mistake. I should have been more descriptive with my "wix.zip" > reference. > I was referring to the wix-16a8b5dbf828f92e28138ce3c9ee852affeaa1ef.zip. > > Just curious, since I have you attention, but what is the preferred method > to using the existing wixBA? > Is it first creating a new solution in visual studio then adding the wixBA > and core projects? Or what I mentioned above in my previous post in order > to get things to work? I would like to prevent others from having this bad > experience. > > Thanks, > Lino > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Cannot-view-RootView-xaml-file-in-visual-studio-2010-tp7596500p7596570.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Cannot view RootView.xaml file in visual studio 2010
Hm, the wix.zip files that are on wixtoolset.org is names wix32-binaries.zip etc? On Wed, Aug 27, 2014 at 2:49 PM, linos wrote: > Hi Rob, > > My mistake. I should have been more descriptive with my "wix.zip" > reference. > I was referring to the wix-16a8b5dbf828f92e28138ce3c9ee852affeaa1ef.zip. > > Just curious, since I have you attention, but what is the preferred method > to using the existing wixBA? > Is it first creating a new solution in visual studio then adding the wixBA > and core projects? Or what I mentioned above in my previous post in order > to > get things to work? I would like to prevent others from having this bad > experience. > > Thanks, > Lino > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Cannot-view-RootView-xaml-file-in-visual-studio-2010-tp7596500p7596570.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Options for pausing the download and installation in wix custom BootStrapper
What if you do something clever in OnResolveSource?, it looks like the WixBA does something for retrying downloads there, I don't understand how it works, but... On Tue, Aug 26, 2014 at 2:09 PM, Balaji R wrote: > Hi, > > Can you please tell which is the correct event in BootstrapperInstallEvent > to pause the download and also please explain the process to pause the > download ? > > Thanks in advance > > Regards, > Balajj R > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Options-for-pausing-the-download-and-installation-in-wix-custom-BootStrapper-tp7596512p7596550.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Customizing BA for Burn/Bundles
Great!, thanks, this looks very usefull On Mon, Aug 25, 2014 at 11:08 PM, Phill Hogland wrote: > Here is a tutorial on using a mba: > > http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/ > > The WixBA is used in the wixtoolset setup. So unlike the WixStdBA, it is > not packaged as a module that can be included in your project. It is > specific to the needs of the Wixtoolset setup. But it is still a good > working example of how you can write your own mba. > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customizing-BA-for-Burn-Bundles-tp7596514p7596533.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Customizing BA for Burn/Bundles
ah, thanks. When I'm using this element: BootstrapperApplicationRef Id='WixStandardBootstrapperApplication.RtfLicense' I'm using the C++ one then?, does it exist any examples that uses this WixBA to get an startingpoint on how I can reference it from wxs? On Mon, Aug 25, 2014 at 6:24 PM, Hoover, Jacob wrote: > The MSI UI is limited by windows installer. The BA UI as no such > limitations. > > https://github.com/wixtoolset/wix3/tree/develop/src/Setup/WixBA is the BA > for Wix > > -----Original Message- > From: Asbjørn Mikkelsen [mailto:asbj...@neslekkim.net] > Sent: Monday, August 25, 2014 11:20 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] Customizing BA for Burn/Bundles > > Would that be the code that is here? > https://github.com/wixtoolset/wix3/tree/develop/src/ext/BalExtension > mba = WixBA? > > I was hoping that one could use the same formats for the squences, > languages, and ui definitions as one do for pure msi, but that is probably > run by something else that is not part of wix? > > > > On Mon, Aug 25, 2014 at 5:46 PM, Hoover, Jacob > > wrote: > > > Both WixStdBA (C) and the WixBA (C#) have source code available to > > learn from. Since everyone wants a different look/feel and work flow, > > the bundle customization is often left up to a custom BA. For a > > vanilla install, WixStdBA does a good job, but injecting new pages > > isn't possible without coding. If you are using .Net for your > > application, I'd strongly suggest starting with a C# BA. This will > > allow you to do a full blown .Net UI, with all the customization you > > want, and then just property drive your MSI's. > > > > The second option would be to modify the Options page of WixStdBA to > > include some check boxes for your feature selection, but I don't think > > that would give you the optimal workflow that you're expecting (a user > > would have to click Options before hitting install). > > > > -Original Message- > > From: neslekkim [mailto:asbj...@neslekkim.net] > > Sent: Monday, August 25, 2014 9:55 AM > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] Customizing BA for Burn/Bundles > > > > I'm creating lots of small msi's so I can modularize my installation > > package, and have been using the bundle feature (Burn?), to make an > > Exe that can install everything. > > > > The problem with this is the UI.. I have somewhat managed to make UI > > in the MSI, but I cannot use that UI, and need to make an UI in the > > Bundle package instead. > > It seems like I cannot use any the ui features that have been aquired > > for MSI, so Have to relearn everything in an totally different > > "language" for bundles.. Where can I find docoumentation on this > > format?, the Theme files seems to be kinda easy to manipulate, but i > > cannot find any information about sequence?, or adding other "pages"? > > What I need, is to implement some form of featureselection, not many > > selections, but a few, does it exist any bundle projects out there > > other than the wix installer (which is just a few pictures to click > > on), that show how to do this? > > > > Or is the idea that everyone need to make their own Bootstrapper > > application? > > > > > > > > -- > > View this message in context: > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customiz > > ing-BA-for-Burn-Bundles-tp7596514.html > > Sent from the wix-users mailing list archive at Nabble.com. > > > > > > -- > > > > Slashdot TV. > > Video for Nerds. Stuff that matters. > > http://tv.slashdot.org/ > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > -- > > > > Slashdot TV. > > Video for Nerds. Stuff that matters. > > http://tv.slashdot.org/ > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > -- > mvh > Asbjørn > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > _
Re: [WiX-users] Customizing BA for Burn/Bundles
Would that be the code that is here? https://github.com/wixtoolset/wix3/tree/develop/src/ext/BalExtension mba = WixBA? I was hoping that one could use the same formats for the squences, languages, and ui definitions as one do for pure msi, but that is probably run by something else that is not part of wix? On Mon, Aug 25, 2014 at 5:46 PM, Hoover, Jacob wrote: > Both WixStdBA (C) and the WixBA (C#) have source code available to learn > from. Since everyone wants a different look/feel and work flow, the bundle > customization is often left up to a custom BA. For a vanilla install, > WixStdBA does a good job, but injecting new pages isn't possible without > coding. If you are using .Net for your application, I'd strongly suggest > starting with a C# BA. This will allow you to do a full blown .Net UI, > with all the customization you want, and then just property drive your > MSI's. > > The second option would be to modify the Options page of WixStdBA to > include some check boxes for your feature selection, but I don't think that > would give you the optimal workflow that you're expecting (a user would > have to click Options before hitting install). > > -Original Message- > From: neslekkim [mailto:asbj...@neslekkim.net] > Sent: Monday, August 25, 2014 9:55 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Customizing BA for Burn/Bundles > > I'm creating lots of small msi's so I can modularize my installation > package, and have been using the bundle feature (Burn?), to make an Exe > that can install everything. > > The problem with this is the UI.. I have somewhat managed to make UI in > the MSI, but I cannot use that UI, and need to make an UI in the Bundle > package instead. > It seems like I cannot use any the ui features that have been aquired for > MSI, so Have to relearn everything in an totally different "language" for > bundles.. Where can I find docoumentation on this format?, the Theme files > seems to be kinda easy to manipulate, but i cannot find any information > about sequence?, or adding other "pages"? > What I need, is to implement some form of featureselection, not many > selections, but a few, does it exist any bundle projects out there other > than the wix installer (which is just a few pictures to click on), that > show how to do this? > > Or is the idea that everyone need to make their own Bootstrapper > application? > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customizing-BA-for-Burn-Bundles-tp7596514.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How does WiX auto-generate GUIDs?
Read the last paragraph here: http://wixtoolset.org/documentation/manual/v3/howtos/general/generate_guids.html On Sun, Aug 24, 2014 at 2:29 AM, Nicolás Alvarez wrote: > Currently I'm using explicit GUIDs for all my components (except > harvested ones). It would make my code much simpler if I used Id="*" > and let WiX auto-generate them. The documentation says the generated > GUIDs are "stable", but I feel like I would trust them better if I > understood how they are generated under the hood :) > > Is there documentation on how they are generated? What changes to the > component would cause the generated GUID to change? > > Thanks, > -- > Nicolás > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: [SPAM] Re: V C++ 2013 redist detection
The point is that vcredist installs side by side, lots of applications are dependant on it, so it shouldn't be removed, but there is newer a problem installing one, even if there is one or many from before. On Fri, Aug 15, 2014 at 8:19 PM, Jeremiahf wrote: > "In fact, I recommend against using any search for the VC runtime. They > use the WixStandardBootstrapperApplication/@SuppressDowngradeFailure > option, so you can safely always chain your desired VC runtime version. > If it's outdated, nothing happens." > > So this is def a bad way to handle this even though the application getting > installed depends on it? > > > On Fri, Aug 15, 2014 at 10:56 AM, Jeremiahf wrote: > > > Thanks guys but I need to detect if it is installed through an msi and > not > > a bootstrapper. It also has to be the x86 version. > > I was trying to detect it through the registry as I have done for > previous > > versions of V C++ Redists. Any idea's? > > > > Sorry for the lack of info in my initial email. > > > > Thank you again, > > > > J > > > > > > On Fri, Aug 15, 2014 at 9:38 AM, Phill Hogland > > wrote: > > > >> Bob; Thanks for the advice. Sorry for posting incorrect x64 code in > the > >> first post. > >> > >> > >> > >> -- > >> View this message in context: > >> > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/V-C-2013-redist-detection-tp7596368p7596376.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 > >> > > > > > > > > -- > > "They may forget what you said but they will never forget how you made > > them feel." -- Anonymous > > > > > > -- > "They may forget what you said but they will never forget how you made them > feel." -- Anonymous > > -- > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX burn: how to change 'WixBundleName' in bootstrapper application?
Bumdle != Bundle ? On Thu, Aug 14, 2014 at 2:32 PM, linos wrote: > In my bundle element I have an attribute Name, I would like to edit this > during an install after a user has selected which application they would > like to install. How can I accomplish this task? I tried the following > below, but no luck. > Manufacturer="Testing" UpgradeCode="C82A383C-751A-43B8-90BF-A250F7BC2863"> > > I took the name WixBundleName from the following link. > > http://wixtoolset.org/documentation/manual/v3/bundle/bundle_built_in_variables.html > > I received the following error... > Error 6 The localization variable !(loc.WixBundleName) is > unknown. Please > ensure the variable is defined > > > Also, in my BA class file, I have the following to edit this variable. > this.Bootstrapper.Engine.StringVariables["WixBumdleName"] = > customProductName; > > Thanks InAdvance. > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-burn-how-to-change-WixBundleName-in-bootstrapper-application-tp7596357.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 > -- mvh Asbjørn -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn bundle with No UI for Bootstrapper Application
I would guess that one reason could be that the gui seems to be very different in the BA compared to MSI, when using Wix, you have good ui libraries for MSI, but almost nothing for BA, as far as I have found. And what is there, is very much diffent, atleast that is my expression right now, doing my rounds with BA that installs lot of MSI's. On Wed, Aug 13, 2014 at 8:56 PM, Hoover, Jacob wrote: > Possible yes, advisable no. If you are using burn, create a custom BA (or > use WixStdBA). > > One of the core reasons for burn (besides chaining multiple prerequisites, > on the fly downloads of needed files, etc) was to provide a single unified > installation experience. While some minimal effort has been done to support > it, it isn't the recommended path. What I would ask is why you need to > display an internal UI on uninstall, and then ask why you can't ask for > that same information from your BA and property drive your MSI. > > -Original Message- > From: Robert Harrison [mailto:robert.harri...@citrix.com] > Sent: Wednesday, August 13, 2014 1:03 PM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] Burn bundle with No UI for Bootstrapper > Application > > Sorry, I forgot the subject in original email. > > I have a burn bundle that uses the built-in WiX Bootstrappre UI. Is it > possible to silence this UI on uninstall and only display the UI of one the > MSI packages? Or maybe have a bootstrapper application with No UI? > > -Original Message- > From: Robert Harrison [mailto:robert.harri...@citrix.com] > Sent: Tuesday, August 12, 2014 11:48 AM > To: General discussion about the WiX toolset. > Subject: [WiX-users] (no subject) > > I have a burn bundle that uses the built-in WiX Bootstrappre UI. Is it > possible to silence this UI on uninstall and only display the UI of one the > MSI packages? Or maybe have a bootstrapper application with No UI? > > > -- > ___ > 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 > > > -- > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Making Heat output binder variables
I don't know what you means with binder variables, but we added this parameter to heat: PreprocessorVariable="var.SourceRootFolder" and that gives us this in the file element: On Sun, Jul 6, 2014 at 7:56 AM, Rob Mensching wrote: > Transform? > > ___ > FireGiant | Dedicated support for the WiX toolset | > http://www.firegiant.com/ > > -Original Message- > From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] > Sent: Friday, July 4, 2014 8:40 PM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Making Heat output binder variables > > How do I make heat output !(bindpath.foo) variables in the File/@Source > attributes? > > No matter what I try, I get $(bindpath.foo). I only get !() if I use a > variable that starts with "wix." like "-var wix.foo". The -wixvar option > (documented as "generate binder variables instead of preprocessor > variables") doesn't change the output. > > -- > Nicolás > > > -- > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows Winner > of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- mvh Asbjørn -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Torch output, how to force wixmst XML output instead of CAB
Americans don't notice this, but the Norwegian language have some letters in ASCII, æøå, and those render ok in normal ascii files, but if the file is UTF-8 they are encoded as unicode in the files (16bit), whereas the rest of the text in the file is 8bit. On Fri, Jun 13, 2014 at 9:53 AM, Rob Mensching wrote: > I always get this mixed up but I thought that ASCII was basically a subset > of ANSI and UTF-8 and they all look the same (unless you write a BOM) until > you use non-ASCII characters. The grand majority of internal WiX goo is > ASCII without a BOM so it all looks the same... > > I think Joel agrees with my memory ( > http://www.joelonsoftware.com/articles/Unicode.html): > > This has the neat side effect that English text looks > exactly the same in UTF-8 as it did in ASCII, so > Americans don't even notice anything wrong. > > ___ > FireGiant | Dedicated support for the WiX toolset | > http://www.firegiant.com/ > > -Original Message- > From: Tunney, Stephen [mailto:stephen.tun...@nuance.com] > Sent: Thursday, June 12, 2014 6:25 PM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] Torch output, how to force wixmst XML output > instead of CAB > > Also, I have been looking at this file in more detail. > > The file itself is encoded with ANSI, but the XML header tag states that > the XML is in UTF-8. Is this intentional? > > -Original Message- > From: Tunney, Stephen [mailto:stephen.tun...@nuance.com] > Sent: June-12-14 9:01 PM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] Torch output, how to force wixmst XML output > instead of CAB > > Speaking of evil things... might I make a suggestion that two files be > output? > > TransformX.wixmst (XML file) > TransformX.wixmst.cab (paired cab file) > > This would be super ideal and would help keep separation of concerns for > each file sane as well. > > Or would that break too much stuff? Can I add a command line argument to > split these things up? Would anyone be opposed to that? > > From: Bob Arnson [b...@joyofsetup.com] > Sent: June 12, 2014 6:41 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Torch output, how to force wixmst XML output > instead of CAB > > On 6/12/2014 3:40 PM, Tunney, Stephen wrote: > > I had posted this question earlier but I guess it got lost in the > > piles of emails going out to your adoring fans ;) > No, I'm just busy. :) > > > In my torch command I have -xi -xo set, and I'm still getting a cab file > with a .wixmst extension? How do I force this to be the expected XML file? > What causes the conversion to a cab file in this case? > If the output contains a file, it's stored as an XML file with a .cab at > the beginning. There's no option to force WiX to not store the files in the > output. > > -- > sig://boB > http://joyofsetup.com/ > > > > -- > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems Open Source. > Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems Open Source. > Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems Open Source. > Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploratio
