Possible, but IMHO somehow a hack. In general a brief description how to do it:
- Do not publish MSI in ARP
- Populate
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\PRODUCTNAME
manually. Think there should be possible to place there a key with a
repair parameter (I did it only with a
Hi,
Assume I have a bundle consisting of 1 MSI + 1 EXE and Exe doesn't support
repair. Is there a way to configure the exe that burn does no repair action
for the exe but for the MSI? like e.g.
ExePackage SourceFile=myExe.exe Permanent=yes AllowRepair=no /
MsiPackage SourceFile=myMsi.msi /
Best
[09D4:09E8][2013-03-01T01:12:43]: Variable: WixBundleTag =
[09D4:09E8][2013-03-01T01:12:43]: Variable: WixBundleVersion = 1.0.0.0
[09D4:09E8][2013-03-01T01:12:43]: Exit code: 0x80070001, restarting: No
2013/3/1 Bob Arnson b...@joyofsetup.com
On 28-Feb-13 09:08, Tobias S wrote:
Assume I have
Is it reasonable to allow PayloadGroupRef as a child for Bundle? Got the
below mentioned configuration where I didn't see the temporary extracted
payload in file system + log file (and so was spending some time in
investigating).
IMHO Payload Element and PayloadGroupRef Element should have same
Hi,
Following scenario:
WiX 3.6, build same solution as 2 bundles: one all containing for the web
and another for a CD image.
Now I have the issue that PackageWeb runs even when PackageCD is already
installed. Digging in the mailing list I understood that here some
kind of BundleID
is set at each
The
/s /vREBOOT=ReallySupress /qn /l*v %temp%\MyExe.log
seems a command for an InstallShield exe which wraps an MSI. Is it possible
to use the MSI directly ?
--
Try New Relic Now We'll Send You this Cool Shirt
New Relic
Regarding layout-only payloads: For us we use much additional payload e.g.
documentation, videos, CD Browser content and so on for CD image layout ...
mostly handled now by msbuild copy as here e.g. things like recursive
copying of **\*.pdf possible.
2013/4/22 Rob Mensching r...@robmensching.com
Not a question but maybe something helpful if you need to compare 2 MSI or
Burn log files e.g. for figuring out what's going wrong with an
installation.
Normally you have something like
MSI (s) (C8:B8) [05:43:18:174]:
or
[05B0:08DC][2013-07-04T05:46:47]:
as a timestamp at the beginning of many
At first glance I'd say to SuppressSignatureVerification=yes but that's
already done. What about keeping the SQL install locally without
downloading and therefore modify the ExePackage definition accordingly?
(Remove everything beginning with RemotePayload... Or what about re-sign
the SQL
Maybe as additional information: A good dialog editor is the
SharpDevelop in a version 3.2.1 or 4.0.1.7090 (available here
http://build.sharpdevelop.net/buildartefacts/) . Older versions of 4.0
have exceptions when editing dialogs.
In general SharpDevelop is able to edit a standalone dialog as
Hi,
Have a look at the wix included tool setupbld.exe. Think this should
be able to create a setup.exe wrapper which runs as admin. But afaik
no possibility to generate a log file.
Other options are full bootstrappers like DotNetInstaller of Burn
which is under development. Visual Studio 2010
Did you consider administrative installation
(http://msdn.microsoft.com/en-us/library/aa367541%28v=vs.85%29.aspx) ?
Unfortunately I'm not well informed about this technique but it might
be interesting for the described scenario.
Regards
Tobias
2011/2/17 Rob Mensching r...@robmensching.com:
1.
For the uninstall handler (meaning the application which uninstalls
the MSIs) I'd recommend to use the UpgradeCode to query the
ProductCode to get more flexibility. Following DTF code sample
illustrates that and uninstalls here the Microsoft SQL Server Compact
3.5 (or other versions sharing the
ICE validation needs an interactive account or Admin privileges to be
happy. See e.g.
http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/11/14/wix-projects-vs-tfs-2010-team-build.aspx
or http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg34102.html
2011/2/18 Peter Solomon
1. You need Burn (Beta state in Wix 3.6), DotNetInstaller, MSI Factory
Bootstrapper Generator or VS2008 (2010) bootstrapper for WiX
2. Possible in WiX by modifying integrated dialogs (comp.
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm ),
also with help of SharpDevelop in a
You have to overwrite the default WiX dialog e.g. in WixUI_InstallDir
with a modified LicenseAgreementDlg.wxs:
1.) get the WiX Source code
2.) from there add copies from
src\ext\UIExtension\wixlib\WixUI_InstallDir.wxs +
LicenseAgreementDlg.wxs to your solution renamed as
Ok, knew there exists an english speaking tutorial:
http://weblogs.sqlteam.com/mladenp/archive/2010/04/15/WiX-3-Tutorial-Custom-EULA-License-and-MSI-localization.aspx
2011/2/18 Tobias S tobias.s1...@gmail.com:
You have to overwrite the default WiX dialog e.g. in WixUI_InstallDir
with a modified
You can use the -t:xsl (transform harvested output with XSL file)
parameter to use a XSL-transform. A sample XSLT can be found here:
http://www.wixwiki.com/index.php?title=Heat or search this mailing
list e.g. at http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/
for some samples.
Hi,
Think there is no way to directly do that as the Difxapp has, as you
stated already, no element for that.
I'd check the issue what is going wrong with the device driver instead
of Resume on error. Do you have e.g. the correct files integrated in
the Installation ? Once I had such an issue
Without deeper knowign the issue: Are you trying to run an MSI from
another one ? If yes: Not recommended! The only workaround is to abuse
the InstallUI sequence for such an approach. This fails e.g. if user
runs installer without UI! A short fragment to illustrate such an
approach:
CustomAction
Just as additional information if you want to run several MSIs: For
sure a bootstrapper or chainer application to do so would be the
recommended solution.
Tobias
2011/2/25 Tobias S tobias.s1...@gmail.com:
Without deeper knowign the issue: Are you trying to run an MSI from
another one ? If yes
Not sure whether you mean the Acrobat Reader or another Acrobat
product. If it's the reader did you think of finding the default
application for pdf files ? This can be archived with a CA by
traversing the reg keys
string defaultApplication =
Alternatively you can use the BinaryWrite CA from
http://msiext.codeplex.com/ to extract binaries from a binary stream
http://code.dblock.org/Source/msiext/1.2/Docs/_msi_binary_8h.html#ae1b642e8fa3ad62c069a7a76eb90f688
should be the direct link to the CA documentation.
DTF should have some
Some construct referencing the corresponding File ID (Here quick
dirty for a MSI DLL) ?
CustomAction Id=NewCustomAction1 FileKey=twain_32.dll DllEntry=test /
2011/3/8 Mark Tempel mark.tem...@shavlik.com:
I'm trying to avoid including the file in the binary table because it is an
extra 900K
Afaik not possible the way you are planing it. Just did a test with
modifying the NEXT button on a CustomizeDlg with following code:
Control Id=Next Type=PushButton X=236 Y=243 Width=56
Height=17 Default=yes Text=!(loc.WixUINext)
Subscribe Event=SelectionNoItems
Think there is no direct flag. Use a xslt to transform the generated
file instead. In http://www.wixwiki.com/index.php?title=Heat there
exists a sample how to do so.
Best regards
Tobias
2011/3/8 Thai-Hoa Nguyen taiwa...@hotmail.com:
When running heat.exe, what flag do I use to turn on the
Hi, Just did a build with the same things in our build environment.
The two MSIs differ only in (except language string) Product Language
Property (1033 and 1040). The transform then is created with Torch.exe
-t Language en-US\SetupProject.msi it-IT\SetupProject.msi -out
en-US\it-IT.mst. Did you
Maybe some words to good sources. Unfortunately for the english
speaking community they are all written in German. Andreas Kerl wrote
several good books about Windows Installer. See
http://www.installsite.biz/de/buecher.htm (German!) for an overview.
There also the english speaking books for
Hi,
Assume this is a limitation of textbox element in Windows Installer
(comp. e.g.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/multiline-edit-control-type-td4176815.html
).
The only point to ensure a better usability here from my point of view
would be to make the edit wider
it works great :)
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 12 March 2011 13:07
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Multilanguage install
Hi, Just did a build with the same things in our build environment.
The two
For the storing in the MSI package:
When diffing it with InstED (unfortuanelty IS2010 and MSIDiff seem not
being able to show it) you can see a substorage element (_Storages)
where the german transform is stored in.
Regards
Tobias
2011/3/17 Tobias S tobias.s1...@gmail.com:
Hi Francesco
Francisco,
When you get it working with the transform msiexec /i installer.msi
TRANSFORMS=:1034. (I'm wondering about the :1034 - should be e.g.
1034.mst???) this means it is working with your produced spanish
transform applied to the english one. So when going back to
InstallSite your problems
for
transform generation is needed.
2011/3/17 Tobias S tobias.s1...@gmail.com:
Francisco,
When you get it working with the transform msiexec /i installer.msi
TRANSFORMS=:1034. (I'm wondering about the :1034 - should be e.g.
1034.mst???) this means it is working with your produced spanish
a really good thread that deserves
attention? E-Mail Me
- Original Message
From: Tobias S tobias.s1...@gmail.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Thu, March 17, 2011 4:52:53 PM
Subject: Re: [WiX-users] Multilanguage
/18 Michael Tissington michael_tissing...@ciqual.com:
This looks great - where do I put this?
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 18 March 2011 09:07
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Multilanguage
?
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 18 March 2011 10:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Multilanguage install
You must add a torch task to the AfterBuild target in the wixproj file.
Following
(undocumented tasks)to do the
additional two task to embed the mst files into a single msi?
Currently I'm using WiSubStg.vbs and WiLangID.vbs
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 18 March 2011 10:32
To: General discussion for Windows Installer XML
bad ...
What are the properties for CultureGroup ?
Where does this come from?
Thanks.
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 18 March 2011 11:49
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Multilanguage install
...@ciqual.com:
Instead of using CultureGroup.Identity is there a way to use the Product
Language (for example 1033) ?
I'd like torch to create a file name Language.mst
Thanks.
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 18 March 2011 12:18
To: General
Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
- Original Message
From: Tobias S tobias.s1...@gmail.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Thu, March 17
Hi,
Assume this won't work as the LCID and locale en-IN doesn't exist in
WiX. Try hi-IN and 0x0439 Hindi (India) instead. An overview of the
LCIDs and WiX Culture names you can see in my post
of the translation for hi-In. (Didn't re-check it)
As this language is from minor importance I didn't follow the issue...
2011/3/24 Tobias S tobias.s1...@gmail.com:
Hi,
Assume this won't work as the LCID and locale en-IN doesn't exist in
WiX. Try hi-IN and 0x0439 Hindi (India) instead
Hi Rob,
Just some thoughts to it (even I never had the issue). Maybe they help:
On http://errordecoder.com/system-error-codes/3/code-1021.html I found
some points which could be from interest:
* Device Driver Conflicts
* Hardware Malfunction
Is it only one system where it occurs ?
Hi,
At first glance for me the two files product and pacack.xml seem to
have the wrong content.
As you describe your requirements have a look at SQL Server Compact
Edition Prerequisite as it has a similar structure and the intention
to install MSI packages.
Pleaase therefore diff the whole
of WiX?
Best regards,
Grzegorz Borczuch
2011/3/24 Tobias S tobias.s1...@gmail.com:
Regarding the localization of hi-in. This localization contains the english
strings which is confirmed to be a bug (comp.
http://sourceforge.net/tracker/index.php?func=detailaid=3163411group_id=105970atid
I read about that, as stated by Neil,
useLegacyV2RuntimeActivationPolicy must be set to true to prevent
issues
(http://siderite.blogspot.com/2010/07/msi-custom-action-error-2896-on-windows.html).
But if I want the code not to run on FW 2.0 is it possible to not
allow the Runtime by commenting
26, 2011 at 8:16 AM, Tobias S tobias.s1...@gmail.com wrote:
Hi,
At first glance for me the two files product and pacack.xml seem to
have the wrong content.
As you describe your requirements have a look at SQL Server Compact
Edition Prerequisite as it has a similar structure and the intention
.
Based on my test and your comment the prereq will Not run via clicking on
the setup.exe so the user will be required to make that choice themselves.
Correct?
On Tue, Mar 29, 2011 at 2:32 PM, Tobias S tobias.s1...@gmail.com wrote:
Try BootstrapperItems=@(BootstrapperFile) instead
You could use a custom action to generate such a string out of the
property PrimaryVolumeSpaceRequired.
2011/3/31 Pally Sandher pally.sand...@iesve.com:
MSDN appears to say you can't. See
http://msdn.microsoft.com/en-gb/library/aa368608.aspx
Palbinder Sandher
Software Deployment Engineer
The point here is that you are using a multi package transaction. So
the whole Install Execute transaction can run either as x86
transaction or x64 transaction if there are only x64 pacakges in
the transaction but not as combined one where x64 packages are treated
as they should (e.g. targeting
No unfortunately WiX ( and the underlying Windows Installer) doesn't
support that scenario to select a file. Only Folder is possible.This
requirement can be solved e.g. by a custom action in c# (+DTF) showing
such a dialog.
Or check the CA File Browse Dialog on
Hmm... MSI still is not able to do so.
The ThmUtil is something completely new in WiX 3.6. I assume it is
used for modelling the Burn Bootstrapper UI (Schema for describing
Theme files processsed by thmutil is written in the help). But as it
is very new few information about it and how to use it
So if I understand your requirements correctly you want to have a
combobox just for selecting a language for the license agreement?
That should be possible by adding a combobox e.g. on the first
installation scren and afterwards set a property for the selected
language and use this value for the
HI,
Think this is a bit more tricky:
Control Id=LicenseText Type=ScrollableText X=20 Y=60
Width=330 Height=140 Sunken=yes TabSkip=no
Text SourceFile=!(wix.WixUILicenseRtf=$(var.licenseRtf)) /
/Control
adds the source file for the ScrollableText during binding of the
installation. Actually
Use zh-TW instead. Zh-HK is a known issue that localization is incorrerct:
http://sourceforge.net/tracker/?func=detailaid=3162829group_id=105970atid=642714
http://sourceforge.net/tracker/?func=detailaid=3163411group_id=105970atid=642714
zh-HK and zh-TW differ in few strings and my company uses
Hm interesting point. The term CD I hear for the first time. When I
understand it correctly this means to deploy to the customers as
frequent as possible.
Back to CI: Imho here the whole company (team) testing strategy should
be taken into account. One aspect of CI are short builds and some unit
Check out src\Setup\Msi\Lux.wxs or src\Setup\Msi\VStudio.wxs from wix
sources for a working sample:
Component Id=VSSchema2005
Guid=7150C0A6-5626-48B6-AA4C-671754E22706 KeyPath=yes Win64=no
Directory=TARGETDIR
CopyFile Id=CopyWixSchema2005
DestinationProperty=VS2005_SCHEMAS_DIR FileId=wix.xsd /
afaik not possible except for modal dialogs. Assume here Tramontana
shows such one.
By default this is not a possible requirement for Windows Installer.
Regards,
Tobias
2011/4/27 william lee wele...@gmail.com:
Hi,
I searched a lot online, but did not hit a result.
The question is how the
hmmm ... just, by accident figured out something interesting. The [X]
seems to correspond with the [Cancel] Button. So when removing the
Cancel button the Dialog Close / [X] gets disabled. Unfortunately
this seems not be working for the ExitDialog.
2011/4/27 Tobias S tobias.s1...@gmail.com
: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: Wednesday, April 27, 2011 5:13 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] old unanswered question regarding to Dialog Close
button
hmmm ... just, by accident figured out something interesting. The [X
Maybe you should consider to use the VCRedist installer instead of the
merge module.
Actually that's not the recommended way as you e.g. have to run an
installer in InstallUI sequence but it works (saw it also e.g. in
OpenOffice installer). The recommended way for installing the VCRedist
in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
G20 0SP
Email Disclaimer
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 28 April 2011 08:47
To: General discussion for Windows Installer XML toolset.
Subject: Re
and
InstallExecuteSequence. So a set property CA must be implemented...
2011/4/28 Bob Arnson b...@joyofsetup.com:
On 28-Apr-11 09:52, Tobias S wrote:
- With this implementation the VCRedist installer runs at a point
where the user can run the installation unattended (for bootstrapper
normally waiting
installed.
2011/4/28 Jeremy Farrell jfarr...@pillardata.com:
From: Tobias S [mailto:tobias.s1...@gmail.com]
...
- Most installs run in UI mode
Interesting, where did you get that information from? What's the ratio
between UI-mode runs and silent, and how accurate is the estimate believed
='LaunchConditions'Not Installed And Not
VC2010REDIST_X86/Custom
/InstallExecuteSequence
/Include
- End: VC2010Redist_x86.wxi -
2011/4/28 Tobias S tobias.s1...@gmail.com:
Assumption based on personal experience as we ran at least the last 4
years the VCRedist during InstallUI. We nerver got
there
could be some trouble handling uninstall since it would be hard to determine
whether the redistributable should be uninstalled too (and in that case, we
would need to make some magic to uninstall it right?)
Thanks both for your time and advice.
Francisco
2011/4/28 Tobias S tobias.s1
Hi Helge,
Please consider e.g.
http://www.installsite.org/pages/en/msi/articles/embeddedlang/index.htm
(also available in German ;-) ). There is discussed an approach
without bootstrapper (think also with a discussion about the needed
transform generation):
The described behavior sounds familiar. Assume the device driver is
not WHQL signed.For Win XP there is no workaround and you have a) do
the WHQL certification b) accept the situation with the driver
wizzard.
Also there should be a dialog Windows can't verify the publisher of
this driver for Win
Hi,
maybe a bit late.. but better late then never ;-)
Got the issue when installing using reduced mode (msiexec /i
MySetup.msi /l*v MyLog.log /qr):
...
MSI (c) (74:0C) [07:19:07:760]: Doing action: WelcomeDlg
Action 7:19:07: WelcomeDlg.
Action start 7:19:07: WelcomeDlg.
DEBUG: Error 2726:
- Did you customize LicenseAgreementDlg.wxs accordingly ? A tutorial
to do so can be found here:
http://weblogs.sqlteam.com/mladenp/archive/2010/04/15/WiX-3-Tutorial-Custom-EULA-License-and-MSI-localization.aspx
(Or a german speaking blog
In general the given WiX translation should fit the UI already and I'd
consider only doing a short test of the given WiX translation. Maybe
check if the longest string (checked with Orca or InstEd in table
Error) fits. For the custom strings the same...
Regarding language placeholders and layout.
Tobias S tobias.s1...@gmail.com
In general the given WiX translation should fit the UI already and I'd
consider only doing a short test of the given WiX translation. Maybe
check if the longest string (checked with Orca or InstEd in table
Error) fits. For the custom strings the same...
Regarding
Did you consider building it by a batch call of MSBuild with the
solution and platform like
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe
MyWixInstaller.sln /p:Configuration=Release /p:Platform=x64
?
2011/5/30 Francisco Gabriel Malbrán fgmalb...@gmail.com:
Hey there.
I am doing a
anyway? and what for? I cant seem to
find any useful information regarding this.
Thanks and regards!
2011/5/31 Tobias S tobias.s1...@gmail.com
Did you consider building it by a batch call of MSBuild with the
solution and platform like
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe
http://wix.sourceforge.net/ - right hand side below Support - Bug
database (or directly
http://sourceforge.net/tracker/?group_id=105970atid=642714 ). Then
please log in or register at sourceforge and you should be able to
submit it...
2011/5/31 Thomas Svare thomas_sv...@symantec.com:
Hello,
Nope unfortunately not. For a good localization only embedding the
transforms, creating a bootstrapper to select the transform or even
handle the whole MSI installation are possible approaches.
2011/7/11 Brad Lemings b...@rebit.com:
Greetings,
Just wondering if there is an easier way to
this is a distinct possibility.
Just wondering if there is a more illustrative tutorial or example somewhere
that does what you describe?
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: Tuesday, July 12, 2011 12:35 AM
To: General discussion for Windows Installer XML
Interesting approach even checking against a environment property in a
LaunchCondition. Didn't know Windows Installer can do that by default
with using %.
Actually the code sample gives me an
ICE03: Bad conditional string; Table: LaunchCondition, Column:
Condition, Key(s): [%testdir]
This I
Not possible as you need OS type dependent DIFx libraries in the
resulting installer. You can simplify that by include different
fragments for x86 and x64 DIFx drivers like e.g. the following sample
feature:
Driver_x64.wxs
---
?xml version=1.0 encoding=UTF-8?
Wix
If you build the project within votive then add the different wixlibs
for x86 and x64 in Project Properties - Tool Settings - Additional
parameters - Linker
Adding them directly as reference in the Setup Project not possible as
there are needed different ones for x86 and x64.
2011/7/19 Tobias
VS2010 includes the same MSBuild concept than building within MSBuild
directly. Try to build it within VS2010 and then copy the commands
from build output and maybe remove the product.generated.* stuff and
try it that way.
What's the output when building it in visual studio Command Prompt ?
Mean
Hi Rob,
Please correct me if I'm wrong. Elevation is done by the chained
installers itself and not Burn ? If so, and I run several MSI + Exe
packages thereafter each wants elevation. Then I'd highly vote at
least for an ability to embed an admin manifest without need of
mt.exe.
I mean I fully
VMWares seem to be somehow tricky regarding retrieving the revocation
lists to verify the signatures. If your company policies allow does it
work if you connect the VM directly to the internet ? Did you try
different settings for Network Adapter like Host-only + Connect at
power on disabled ?
the bootstrapper on a system without
internet connection.
Cheers,
Thomas
Tobias S tobias.s1...@gmail.com
22.07.2011 11:40
Bitte antworten an
General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
An
General discussion for Windows Installer XML toolset.
wix
Actually I also was the oppinion that
Microsoft.Deployment.WindowsInstaller.Installer.EnableLog(InstallLogModes.Verbose,
logFile + .install.log);
does the same as /L*v. At least I use ith for my implementations that way.
When doing a short diff with winmerge I mentioned just the
Property(S)
it basically comes down to getting the right
flags passed to WinVerifyTrust(), which is unfortunately no easy task.
On Fri, Jul 22, 2011 at 3:35 AM, Tobias S tobias.s1...@gmail.com wrote:
Hi Thomas,
Give it a try on that real restricted testsystem or some other system
without internet
Hi,
will the following scenario be possible with burn:
Have a Select Language dialog to select the current language for
Burn and then show the Burn UI + License Agreement in the selected
language ? All without creating an own custom UI, mean using
WixStandardBootstrapperApplication.RtfLicense or
the code to match the current
user locale with a fallback language. I do not really want to create a
dialog box to select a language up front.
On Thu, Jul 28, 2011 at 7:33 AM, Tobias S tobias.s1...@gmail.com wrote:
Hi,
will the following scenario be possible with burn:
Have a Select
Something like
ItemGroup
MyFiles Include=..\..\..\Binaries\assembly1.dll /
MyFiles Include=assembly2.dll /
MyFiles Include=..\..\..\assembly3.dll /
/ItemGroup
Copy SourceFiles=@(MyFiles) DestinationFolder=$(OutDir)
/Copy
e.g. in target Target Name=BeforeBuild
No, unfortunately not possible due to MSI UI. See also older
discussions in this mailing list in this context e.g.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Edit-Control-trap-textchanged-possible-tt2907541.html.
If really needed I think only a CA dialog is an alternative.
Hi,
Following implementation in burn:
Chain DisableRollback='yes'
PackageGroupRef Id='Netfx4Full' /
PackageGroupRef Id='SQLCE35_SP2_X86' /
PackageGroupRef Id='SQLCE35_SP2_X64' /
PackageGroupRef Id='VC2010SP1REDIST_X86' /
/Chain
All packages are just installing the things which could be guessed
will get that and say a reboot is required.
On Thu, Aug 11, 2011 at 6:33 AM, Tobias S tobias.s1...@gmail.com wrote:
Hi,
Following implementation in burn:
Chain DisableRollback='yes'
PackageGroupRef Id='Netfx4Full' /
PackageGroupRef Id='SQLCE35_SP2_X86' /
PackageGroupRef Id
the intsall immediately and saying a reboot is required
to continue the install? It should be.
On Fri, Aug 12, 2011 at 12:33 AM, Tobias S tobias.s1...@gmail.com wrote:
Yes the netfx error code returning and Burn handling to reboot is
correct. My point is that the reboot is forced and the user has
Hi,
Try to use util:FileSearch for check mfc100.dll version for deploying VCREdist.
SystemFolder works fine on x86 + x64:
util:FileSearch Id=MFC100_Version_x86
Variable=MFC100_Version_x86 Path=[SystemFolder]\mfc100.dll
Result=version/
Doesn't work:
util:FileSearch Id=MFC100_Version_x64
somehow difficult to describe with few background information. So just
some thoughts.
Maybe take the Tramontana tutorial as starting point:
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization. In
general Tramontana seems for me one of the most efficient ways to get
into WiX / MSI.
a) Did you get the drivers installed manually. Think it should work
with context menu on inf driver + install. But to be honest I didn't
do it for a long time ;-)
b) Check out my configuration sample e.g. here:
Is this new component in a feature whose state is not being migrated
correctly by MigrateFeatureStates standard action?
Try to set
MigrateFeatureState=no
--
Get a FREE DOWNLOAD! and learn more about uberSVN rich
sorry, should be
MigrateFeatures=no
2011/8/18 Tobias S tobias.s1...@gmail.com:
Is this new component in a feature whose state is not being migrated
correctly by MigrateFeatureStates standard action?
Try to set
MigrateFeatureState
MigrateFeatures=no...'
Kurt
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: Thursday, August 18, 2011 3:15 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] New file not installed
sorry, should be
MigrateFeatures=no
2011/8
Worth mentioning is IMHO SharpDevelop in a version 4.0.1.7090 (or
higher) for editing dialogs. With help of this tool a standalone
dialog (wxs files from WiX sources like e.g. InstallDirDlg.wxs) can be
opened, previewed and edited in Design view. Combined with Votive it
offers good abilities for
1 - 100 of 210 matches
Mail list logo
