Is ClickThrough still being developed ?
What other options are there for managing (and tracking) automatic updates?
I've tried FlexNet but it seems to be full of holes.
Thanks.
--
Doing More with Less: The Next Generat
I'm needing help trying to build an automated process for the following.
1) Each customer has many clients
2) Same binaries
3) Support for multiple languages
4) msi needs to be branded with customers logos and license agreement
5) Some help files and configuration files are specific to each custom
WiXedit
Although I too am interested in hmne.sourceforge.net / InnoSetup style
Wizard for creation of MSIs officially part of WiX.
On Thu, Sep 8, 2011 at 8:29 PM, Michael Tissington
wrote:
> Is ClickThrough still being developed ?
>
> What other options are there for managing (and tracking) auto
Maybe Indigorose TrueUpdate could fulfill the needed requirements.
Regards
Tobias
--
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
fro
Unless I'm mistaken you'd need to create a different MSI for each
customer...
You could automate the process of building the MSIs via command line
scripts and use preprocessor / environment variables to have the build
process determine which logos, licence agreement and help / config files
to
I would create a single MSI that is UI-less and you can pass parameters to if
you need to change the start menu names etc. This would make updates simple
as there was just one package to update.
I would run this from a custom Chainer of some sort (Burn for instance) that
would allow pluggable logo
Ahh, if you are modifying machine state (I *think* that's what that does)
then you want to put a package in your Chain. Might not matter on Windows
Embedded, but remember that the BA does not run elevated so it cannot modify
the machine. In this case, I'd create a data driven custom action and put
Oh, he mentioned automatic updates?
Well what language is your project written in, and if it has a GUI
component, which library did you use?
On 9/8/11, Tobias S wrote:
> Maybe Indigorose TrueUpdate could fulfill the needed requirements.
>
> Regards
> Tobias
>
> --
> This is exactly what Burn is for in WIX v3.6. That'll keyword will
probably
> get you some really good hits in Bing.
Presently I'm using WiX 3.5, since 3.6 is in beta and I figure if I'm just
learning WiX it's a good idea to stick with stable releases. But if what I
need is only in 3.6, then o
Hi,
When I added more installers to my configuration file (Bundle.wxs) it breaks
the installer. Intially I was having only .msi packages only and it worked
fine.
Is this the way to run several msi packages and exe files in a Bundle.wxs.
I might be doing something really bad here:
-Orlando.
--
Hi
I'm trying to copy a file FOO.DB to the APPLICATIONFOLDER. The FOO.DB can
optionally copied into the same folder like the MSI, but is not included in
the MSI. The FOO.DB is optional; it may be there or not.
If I run the setup interactively it just works. If I'm running it with /qb
the FOO.DB i
/qb means that the user interface sequence isn't run, so make sure your search
(I think there'll be an AppSearch standard action) is in the Execute and UI
sequences.
Phil Wilson
-Original Message-
From: Marc Bauer [mailto:marc@gmx.net]
Sent: Thursday, September 08, 2011 2:15 PM
T
Hi Phil
This is all I have configured myself... so all other actions should have
default order, isn't it? I'm not sure, but until now all have worked well...
On 07-Sep-11 13:24, john.burak wrote:
> I'm curious why WixUI_Advanced uses APPLICATIONFOLDER instead of the
> well-known INSTALLDIR property which Mondo and other popular msi build
> technologies use?
>
> I'm also curious why WixUI_Advanced requires the ApplicationFolderName
> property. I already
On 08-Sep-11 17:06, Orlando wrote:
> When I added more installers to my configuration file (Bundle.wxs) it breaks
> the installer.
You might get more replies if you describe what "breaks" means.
--
sig://boB
http://joyofsetup.com/
---
On 07-Sep-11 12:42, john.burak wrote:
> I'm also curious why WixUI_Advanced needs to put anything in
> InstallExecuteSequence, where Mondo does not. Both dialog sets allow
> the same basic functionality.
WixUI_Advanced supports per-user and per-machine scope selection; none
of the other dialog
16 matches
Mail list logo