Thank you Rob. One thing to mention is that I had used windows forms as
opposed to WPF. Obviously something did not translate over.
Sent via BlackBerry by AT&T
-Original Message-
From: Rob Mensching
Date: Fri, 2 Sep 2011 17:41:23
To: Randy Kroeger; General discussion for Windows
Take a look at the wix36\src\Setup\UX. That's the BA for the WiX toolset. It
isn't perfect (haven't spent time on it lately) but it should show you how
things work.
On Fri, Sep 2, 2011 at 5:01 PM, Randy Kroeger wrote:
> I have built a custom BA and the screens display when the setup is
> executed
I have built a custom BA and the screens display when the setup is executed.
However, my MSI's that I have setup in my bundle, do not execute. I am
OBVIOUSLY missing something and am embarassing sending this email because I
just need to get this done. I looks like I am not exeucting somethi
Sounds like the Merge Modules are broken, most likely around their
"Before/After" sequencing. One thing you might try is adding those actions
to your .wxs InstallExecuteSequence without sequence numbers. Something
like:
The WiX toolset will put the values in with the default (aka: correct)
I've successfully I added the "WixUI_Advanced" UI to my installer and it
works. But now I get these errors:
Error 293 ICE27: 'StopServices' Action in InstallExecuteSequence table in
wrong place. Current: Costing, Correct: Execution light.exe 0
1
Error 294 ICE27: Act
404 errors exist for me for
http://wix.sourceforge.net/manual-wix3/WixUI_Mondo.htm
http://wix.sourceforge.net/manual-wix3/WixUI_Minimal.htm
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log
Strange, still broken for me. Maybe there is something wrong with the
SourceForge server I'm getting in my area. Thanks!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Broken-link-to-Mondo-documentation-page-tp6754555p6755175.html
Sent from the wi
Chris,
Never saw such an issue before but just want to mention a workaround
in my mind. Am I understand you right you are creating a transform
using DTF? If so did you try to use Msitran.exe from Windows Installer
SDK to generate a transform between original and DTF modified MSI
instead?
Maybe In
Sorry for the rapid emails but I now have a much simpler explantion. DTF
behaves the way it does because this is the way MSI behaves. Go figure...
:-)
It seems that after calling MsiDatabaseGenerateTransform you also have to
call MsiCreateTransformSummaryInfo. It's not automatic.
I was able to use KDiff to see there were differences in the two mst files
near the top of the file. That encourage me to open the two files using
the SummaryInfo class in DTF and the result was major differences.
I'm wondering if this is a bug in Database.GenerateTransform(). It seems
like
Haha, yeah this sucks bad. We ended up having to do different upgrade codes
for every instance transform.
Now that sounds simple, and if you have a simple way of doing it I would
love to hear it, but we made a dummy upgrade code, so that the Upgrade table
would be populated with something at build
I've done a lot of multiple instance work ( even within the last couple of
months ). The big reason why I could see why UpgradeCode can't be * is
because it would break major upgrades. The UpgradeCode property is far
stickier then ProductCode and PackageCode.
I've written some code that all
I'm seeing a wierd problem that I've never seen before and I'm hoping
someone has come across it before.
I created a C# application using DTF to programatically make a copy of an
MSI, update the copy and then generate a transform against the original
MSI.
I am able to take this MST and ap
I think there is a feature request open to allow WiX to updated the
UpgradeCode for each instance transform. It just hasn't been implemented.
Same could be done for the ProductCode but I'd have to investigate to see if
there are reasons why "*" isn't allowed right now.
InstanceTransforms always re
Documentation is lacking in this case a little bit. Best bet is to take a
look at how the WiX toolset installs itself (wix36\src\Setup\Bundle). That
does what Tobias is talking about for NETFX and shows how to get the mbapreq
to do the right thing... there may be bugs left yet, of course.
On Fri
I've authored an installation package (with WIX) that uses instance
transforms to allow multiple installations of the package. Although setting
up the initial package was pretty easy, I found out too late that there
seems to be very little guidance on how to *upgrade* existing instances when
a new
The link worked fine for me.
-Original Message-
From: john.burak [mailto:john.bu...@telvent.com]
Sent: Friday, September 02, 2011 12:49 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Broken link to Mondo documentation page?
Is anyone else getting a server error in the follow
Is anyone else getting a server error in the following situation? I clicked
the "Mondo" link on the page
http://wix.sourceforge.net/manual-wix3/WixUI_dialog_library.htm
http://wix.sourceforge.net/manual-wix3/WixUI_dialog_library.htm and got the
error:
/An error has been encountered in accessing
thanks for the very quick response!
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 01 September 2011 14:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Does Wix 3.5 Light.exe support named bind paths
No, unfortunately, th
Personally I solved that in a test implementation with a PackageGroup
and a PackageGroupRef in main bundle.
PackageGroupRef
The proper implementation relys on a file compare of the mfc100.dll in
SystemFolder as the old detection mechanisms (registry detection
ProductCode) frequently used
Hi!
I have such a problem - I need install component which contains ini file
modification always on install and modify. The problem appears when all
features are installed and modify removes one of the features - in that case
no components can be installed.
Maybe there is a possibility to make a h
21 matches
Mail list logo
