Hi
I'm wondering on which approach I should take for files larger than 2 GB in
wix.
I think these are the possibilities:
1) Splitting cab files, since cab files has a limit of 2 GB. Is it possible?
Can WiX somehow do this automagically?
2) Use a custom action to merge in the file, (should be
I have a check box control(checked by default) that launches a web site upon
clicking finish button in the final screen of my installer. And its working
as expected.
My concern is that if I press the ESc key instead of clicking the Finish
button, It exits the installer launching the website.
Hi,
the initial entries for name, version and publicKeyToken are lowercase
in MSIAssemblyName table.
This breaks the Visual Studio(05,08,10) automatism to add the fitting
MergeModule to a Setup Solution.
If i change Name, Version and PublicKeyToken to initial uppercase letters,
my MSMs are
According to Microsoft the CAB file format has an internal limit of
approximately 2 GB - http://support.microsoft.com/kb/836160 There is a
manual workaround for splitting files 2 GB across multiple cabs listed
there which you may be able to use in your WiX project if you use the
-cc -reusecab
I think it sounds like esc is leading to a cancel event. Might disabling the
cancel button on the final page fix it?
Leif
On Mon, Jun 14, 2010 at 3:57 PM, Pally Sandher pally.sand...@iesve.comwrote:
Sounds suspiciously like a Windows Installer issue.
Have you checked verbose logs when you
Thanks for the reply. I guess the only way is to test all options and narrow
it down to the best one.
Cheers,
Leif
On Mon, Jun 14, 2010 at 4:11 PM, Pally Sandher pally.sand...@iesve.comwrote:
According to Microsoft the CAB file format has an internal limit of
approximately 2 GB -
WARNING
Another NOOB alert...
/WARNING
After all of my files get installed, I need to prompt for some additional
configuration information.
I created a custom dialog to do this. It has a couple check boxes on it.
I would like to NOT have this dialog run at all if the user is removing the
More NOOB stuff follows:
The following code doesn't run in the order that I would have expected,
based on the Order= parameters.
I would like to display the ConfigSQLDlg before the ConfigSMTPDlg, but this
actually
happens in the reverse order... SMTP is first, then SQL.
Note that the
regasm /regfile doesn't always work because if you have any user defined
register functions they will not be in the regfile. From what I've seen of
heat, it's not vunerable to this extraction problem. InstallShield does have
this problem.
Personally I wrote a little UI over heat that
1 - Show Dialog=ExtraConfigDlg OnExit=success![CDATA[(REMOVE
ALL) AND NOT Installed]]/Show
2 -
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
and Condition the ExitDialog with Installed in the InstallUISequence
so they're mutually exclusive.
FYI an easier/proper way to
See my reply to your other post try to keep your issues limited to one
thread if they are the same topic (which these pretty obviously are)
otherwise you're going to confuse yourself others when you start
getting replies to one thread advising you to do x when the other thread
is advising you to
It's conditioned with Installed AND (RESUME OR Preselected) so
anything which sets the Preselected Property (such as patching with
MSP's) after your MSI is installed will show it. See
http://msdn.microsoft.com/en-us/library/aa370839.aspx
Palbinder Sandher
Software Deployment IT Administrator
T:
Show Dialog=ExtraConfigDlg OnExit=success![CDATA[(REMOVE ALL) AND
NOT Installed]]/Show
The AND NOT INSTALLED clause solved that problem - thanks Pally...
The reason I can't ask the configuration questions earlier in the install
process is that the installer installs a needed file. After this
Actually, being such a NOOB, I can't see the connection between this post and
the previous one... they do seem to be separate problems to me...
But that said, I'll review and continue this thread if I can't figure it
out.
Thanks again!
--
View this message in context:
Hi Pally (et. al.),
I don't see how this post and the other (previous on from me) are related,
so this question still stands...
TIA
Greg
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Dialogs-out-of-order-tp5177864p5178373.html
Sent from the
What's stopping you asking the user questions in the InstallUISequence
running the DLL function in the InstallExecuteSequence as is standard
practice? Your custom action doesn't need to run immediately as soon as
you gather information from the user, you can still schedule it after
InstallFiles
What's stopping you asking the user questions in the InstallUISequence
running the DLL function in the InstallExecuteSequence as is standard
practice? Your custom action doesn't need to run immediately as soon as
you gather information from the user, you can still schedule it after
InstallFiles
I have the following node (file.dtsConfig):
Configuration ConfiguredType=Property
Path=\Package.Variables[User::path].Properties[Value] ValueType=String
ConfiguredValue\\convs07\Historical
Integration\DataFarm\WIT\Files\/ConfiguredValue
/Configuration
Wix code:
…
Util:XmlFile
I have found a few indications online that heat.exe does not support
converting a .reg file to the WiX .wxs format. The suggestions I ran across
show to use tallow.exe from WiX v2. Is it true that v3+ does not support
this any longer? Also, the download for v2 is broken.
Thanks.
Here are the verbose log snippets:
MSI (c) (CC:94) [22:29:34:875]: Doing action: ExitDialog
Action 22:29:34: ExitDialog.
Action start 22:29:34: ExitDialog.
Action 22:29:34: ExitDialog. Dialog created
MSI (c) (CC:FC) [22:29:44:828]: Doing action: LaunchURL
Action 22:29:44: LaunchURL.
Action
That is correct Heat in WiX 3 doesn't convert reg files. The only route
is to use tallow and then wixcop. It would be nice to get this back, may
one day I'll get around to writing a heat extension to do this.
Neil
-Original Message-
From: Andy Clugston [mailto:clug...@gmail.com]
Sent:
Hi there,
Is there a way, during uninstall of an MSI, to detect presence of some other
MSI and if so, stop/abort uninstallation informing users of presence of the
dependant MSI ?
In other words, given MSI's A and B, is there a way to express dependency
between A and B so that A cannot be
I think you should be able to do this with the Upgrade element:
Upgrade Id=other apps upgrade code
UpgradeVersion Minimum=0.0.0 Maximum=max version IncludeMinimum=no
OnlyDetect=yes Property=OTHERAPPDETECTED /
/Upgrade
You can then use the OTHERAPPDETECTED property in conditions to block the
Upgrade table is not checked during uninstall, so that won't work. You will
need some other means of detecting the dependent installation(s).
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Monday, June 14, 2010 1:42 PM
To: General discussion for Windows
Right. But the problem appears the sfxca is doing .net 4 activation using
deprecated APIs. A separate path will be required.
-john
On Fri, Jun 11, 2010 at 6:41 PM, Bob Arnson b...@joyofsetup.com wrote:
On 6/9/2010 9:04 PM, John Ketchpaw wrote:
Using this config file,
WiX v3.5 contains
If it works using /qb compare the InstallUISequence table versus the
InstallExecuteSequence table. There may be a CA that runs in the
InstallUISequence that needs to the InstallExecuteSequence.
--
View this message in context:
Hi,
I have 6 shortcuts for 6 files and they are in the order 1,2,3,4,5,6. But
on installing 3 is coming after 1st instead of 2. Should we specify the
order?
Please do let me know what's going wrong here?
Regards, Subramanyeswari
--
View this message in context:
27 matches
Mail list logo