Hi Blair,
thanks for the input. I let the whole thing run while also using Process
Monitor to log all
processes being created and you were right:
The last rtpMIDISetup.exe process (showing the erroneous dialog) is
instantiated from
runonce.exe, which itself is instantiated from MsiExec.exe...
Correct me if I'm wrong, but doesn't -layout only download external packages?
I might have been unclear, what I want to do is extract packages that have been
embedded
Within the bootstrapper.
We are doing this so that customers would have the option of using the MSIs
directly for deployment
http://blogs.msdn.com/b/junfeng/archive/2006/09/19/761765.aspx says this:
Be careful about RunOnce registry key: It may run before system restart.
According to KB 281829, RunOnce registry key will run in the following cases:
1. At the end of installation through InstallFromHinfSection even in
I thought that might be the issue as well. I can't find another reference.
So, I made a new solution that only contains a brand new WiX installer
project. The same build errors occur.
1. New 2012 solution, single WiX v3.7 (.msi) project
2. Added manufacturer and uppper-cased UpgradeCode in the
Hi,
thanks for that input as well. My driver's inf-file does not contain any
RunOnce entries.
So I assume that burn is doing that somewhere...
Could Rob or Bob possibly chime in on this? I'd gladly do some more
digging/debugging,
but as I still do not fully understand the overall
Hi,
Got a bundle that installs VS2012 or VS2013 Shells..
I've noticed that sometimes, we get a 0x80048bc7 (pending restart required)
It seems to be if VS updated some .NET framework components...
Our bundle doesn't catch it as 3010 etc... so what does 0x80048bc7 translate
to?
In the VS admin
Classification: Public
You don't need to ADD the WXS file to your project, you only need to copy the
UI element from that file...
Nor do you need to physically copy it to your project either...
If you follow the steps I provided below you will be fine...
1. in your PRODUCT.WXS file add the UI
Hello,
I have a custom dialog box that I’ve successfully inserted between the
LicenseAgreementDlg and InstallDirDlg using WixUI_InstallDir template.
Now I want to use the WixUI_Advanced template and insert the same dialogbox
when user press the “Advanced” or “Install” buttons.
… and I failed
If I understand the issue, I would go to each of the two project files
(Prod.*proj and TEST.*proj), right click on each file and select 'Unload',
then right click and select Edit Prod.wixproj (or TEST.wixproj). Then
compare the working to the non-working file. It sounds like your OutputName
Classification: Public
What does the MSI logging reveal? ( to enable MSI logging check this out:
http://support.microsoft.com/kb/223300)
-Original Message-
From: Pierre-Alain GALTIER [mailto:pierre-alain.galt...@vivelys.com]
Sent: November-06-13 8:58 AM
To:
Ugh! This makes no sense to me...
I moved my UIRef in my Product.wxs outside of the Product section and
added to its own fragment in the Product.wxs file
Fragment
UIRef Id=WixUI_Minimal_Modified/
/Fragment
And removed the reference to WixUIExtension.dll, now it builds? WTF?
Why did
Thank you
When I hit the Advanced button in the Welcome Eula Dialogbox, the next dialog
box is InstallDir and the logging said :
Action 15:57:31: AdvancedWelcomeEulaDlg.
Action start 15:57:31: AdvancedWelcomeEulaDlg.
Info 2898.For WixUI_Font_Title textstyle, the system created a 'Tahoma' font,
The whole fragment is :
UI Id=myWixUI
Property Id=VIV_SelectArchDlg_Back Value=AdvancedWelcomeEulaDlg /
Property Id=VIV_SelectArchDlg_Next Value=InstallDirDlg /
Publish Dialog=AdvancedWelcomeEulaDlg Control=Advanced
Event=NewDialog Value=VIV_SelectArchDlgLicenseAccepted =
Ignore my last message. That didn't work after all, as none of the dialogs
appear in the ui sequence table. So...
I did what Steve suggested and copied the contents WixUI_Minimal into my
Product.wxs (and placed it inside the Product tags). And then renamed
the Id on the UI element to
Classification: Public
Did you remove the WixUI_Minimal.wxs from your project?
I have WixUIExtension referenced in my setup project...
-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com]
Sent: November-06-13 11:37 AM
To: General discussion about the WiX toolset.
Subject: Re:
If you look at the duplicate id error messages, IMO, it is a conflict with
WixUIExtension as the file path for the conflict is from the WiX build
server, not my machine.
On Wed, Nov 6, 2013 at 1:00 PM, Tony yellowjacketl...@gmail.com wrote:
It was never in my project.
On Wed, Nov 6, 2013 at
It was never in my project.
On Wed, Nov 6, 2013 at 11:52 AM, Steven Ogilvie steven.ogil...@titus.comwrote:
Classification: Public
Did you remove the WixUI_Minimal.wxs from your project?
I have WixUIExtension referenced in my setup project...
-Original Message-
From: Tony
Classification: Public
This is from your post below:
3. copied WixUI_Minimal.wxs to the project folder and
renamed it to WiXUI_Minimal_Modified.wxs. Added
WiXUI_Minimal_Modified.wxs to the project.
-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com]
Sent:
Classification: Public
If you read the docs from WIX it is easy:
Inserting a custom dialog into a built-in dialog set You can add custom dialogs
to the UI sequence in a built-in WixUI dialog set. To do so, you must define a
UI/ element for your new dialog. Then, you must copy the contents of
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Custom-Action-which-call-win-32-dll-possible-tp7590295p7590335.html
Sent from the wix-users mailing list archive at Nabble.com.
This works, but I have no idea why as most of the lines that had conflicts
prior to the changes are still present
1. Setup virgin project/solution
2. copied contents of wixui_minimal.wxs into my product.wxs
3. set manufacture and uppercased upgrade code
4. added a single file to install
I should have said this in my last messsage...
Thanks for all of the help and patience.
On Wed, Nov 6, 2013 at 3:03 PM, Tony yellowjacketl...@gmail.com wrote:
This works, but I have no idea why as most of the lines that had conflicts
prior to the changes are still present
1. Setup
Just to close the loop on this, WiX 3.8 will be removing WixPdbPath:
http://wixtoolset.org/issues/4152/
robmen wrote
Many people move it to a drop location that is laid out identically as the
build machine with a different root. We can work with that. pyro already
has support for such
I don't think you want that check. You want Burn to register the package for
each bootstrapper that installs it. In other words, you want to install it
everytime, even if it's already installed. Burn should detect that the
package is already installed and just skip over it. That way, when one
The Property attribute should be the same on both elements. It ties them
together in that way.
According to the MSI documention for the ComboList property:
If the ComboList Control bit is set on a combo box, the edit field is
replaced by a static text field. This prevents a user from entering a
Are you just starting your journey with WiX? If you are, you might take a
step back from WPF user interfaces for a few days and dig into writing an
MSI file. Once you've got that, I'd read up on how to use Burn by itself,
using the UI that comes with the toolset. Here, I'm talking about just
I've read a lot of threads, all of which seem to burn not yet having support
for Instance Transforms. This is a bit of a bummer, as I've already authored
the MSI with the transforms, and just need a bootstrapper for [.net, sql ce,
target iis website selection (install only), instance selection
If the only block to be reported is ?Reboot Pending,? the returned
value is the Incomplete-Reboot Required value (0x80048bc7).
That's Pending Restart due to a Block. Incomplete means, the
installer did not finish. Upon Restart the block should be removed
and the install will need to be
Things to try:
1. Did you replace/remove the old Publish elements that were directing the
user elsewhere? Looks like in the WixUI_Advanced.wxs, there are there
Publish elements, each taking the user somewhere else depending on a
condition.
2. Does your Publish element have an Order property? If
Correct. No one has contributed support for instance transforms yet. It's a
non-trivial feature request. smile/
-Original Message-
From: Lynn Crumbling [mailto:lcrumbl...@kioware.com]
Sent: Wednesday, November 6, 2013 1:42 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
Thank you Phil for the suggestion, but unfortunately it didn't work. The
wixproj files are identical except for guids and descriptions. The OutputName
elements contain just the application names. There was a difference in
ItemGroup order which I changed to make the ordering identical, closed,
Hi,
I am new to WiX and I am evaluating WiX for the company I am working for.
We install windows applications, websites and windows services. We need to
build everything from command line. I need to know whether I can use WiX to
create packages to install websites and windows services. Awaiting a
I'm trying to use the DTF libraries to apply a Patch to an Msi file and then
extract the updated files from the Patched Msi. I can't get it working, and I'm
at wit's end. Any guidance would be much appreciated.
I can apply the patch and transform to the msi, and the Files table in the Msi
then
Yes, all that and more.
-Original Message-
From: Tony Jose Mampilly [mailto:kooltonyj...@gmail.com]
Sent: Wednesday, November 6, 2013 10:03 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] New to Wix
Hi,
I am new to WiX and I am evaluating WiX for the company I am working
Hi,
Thank you for the feedback
Regards
Tony
On Thu, Nov 7, 2013 at 12:14 PM, Rob Mensching r...@robmensching.com wrote:
Yes, all that and more.
-Original Message-
From: Tony Jose Mampilly [mailto:kooltonyj...@gmail.com]
Sent: Wednesday, November 6, 2013 10:03 PM
To:
Hi,
I have made a bootstrapper which wraped around a msi, the custom ba dll was
written using mfc.
When I execute bootstrapper.exe \layout [DestFolder], it just copies the
bootstrapper.exe to the destination folder.
What should I do to make \layout extracting all the files embedded in the
36 matches
Mail list logo
