Hi John,
Thanks for the clarifications. I have come in in the morning and tried
to follow the steps as u have suggested. Attaching my two source files
for your reference.
Below is what i have tried to do today:
* I have created the file trunkdb.wxs using the following command:heat
dir
Hi John,
Please also have a look at the directory structure and registry entry i
am creating. Let me know in case i need a change there as well.
Regards,
Suvra Jyoti
Original Message
Subject:Re: [WiX-users] Referring to fragments
Date: Mon, 18 Nov 2013 13:47:44
Ah, I missed that.
You need to create a reference in your feature to each component, because
now you have components which aren't assigned to any feature, which means
they would never be installed.
Please try this:
1. On your Heat.exe call, specify the -cg argument with a component name:
Hello users,
I am new to WIX toolset and I am very interest to create setup in WIX toolset
but I don't know how to create UI.. Can you people help me to resolve?
With Regards,
Prabu.S [Extn-228],
Software Engineer,
pr...@iinterchange.com
Hi there,
you can customize standard UI if you look at link
http://wix.tramontana.co.hu/tutorial/user-interface-revisited you will find
a tutorial.
If you want really new own UI then look into wix source code, their
installer has custom UI. I think this is the code
Hi John,
I did as you suggested. I was getting the error C:\Program Files
(x86)\WiX Toolset v3.7\bin\TortEngineDemo.wxs(24) : error LGHT0
094 : Unresolved reference to symbol 'Component:TORTDEMO' in section
'Product:{5
A1581BE-27C3-46A1-8699-4F1D642C97E0}'. So i changed the name to TORTDEMO
Hi John,
Any updates on the below issue. I am still stuck there.
Regards,
Suvra Jyoti
Original Message
Subject:Fwd: Re: [WiX-users] Referring to fragments
Date: Mon, 18 Nov 2013 15:06:38 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: John Ludlow
Do those files exist at compilation time? They are C:\Program Files (x86)
paths, and your code doesn't specify a full path in File/@Source. I'm not
sure how it came up with that path, but it's probably wrong, since you are
likely building your application binaries in a build area.
You will need
Hi,
I create msi to install our company software. During installation it's required
to register COM object. it requires admin privileges.
I use the following condition to detect admin privileges
Condition Message=Only administrator is allowed to install the application.
(Privileged and
Hi John,
When I are created the trunkdb.wxs file i had ditected it to
D:\Project\ESI\Code\trunk\db. These files exist now also and are part of
the SVN source control. I do not get what you mean by C:\Program Files
(x86) and I'm not sure how it came up with that path . I am just
executing
Yeah I didn't explain that path thing very well. I was referring to this
path:
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs
This probably shouldn't be here. Best to keep this out of the WiX install
directory. If this is a file which is generated for every build, then
either use an
Also I don’t understand why the 'main' bundle should have Related Bundle
element?:
Main bundle needs a related bundle element set to detect with the GUID
attribute in that element set to the same GUID of the related bundle element
GUID attribute in all the patch or addon related bundles.
Jacob Thanks
I have a major release on which user can install HF1 and HF2 and when
removing HF2 it should return to HF1
The user can also skip HF1 and install HF2
But should not be able to install H1 on top of HF2
On next major release bootstrapper detect that a current major release is
So in the main bundle i need to add
RelatedBundle Id={0E206C2C-82FC-420D-AFA6-FA347F3FDA14} Action=Patch/
Where ={0E206C2C-82FC-420D-AFA6-FA347F3FDA14} is the upgrade code
And in patch I need to add
RelatedBundle Id={0E206C2C-82FC-420D-AFA6-FA347F3FDA14}
Action=Detect/
In order to make
No the other way around. Detect goes into main bundle. Patch goes in patch
bundle.
By upgrade code what are you referring to? The upgrade code of the main bundle?
-Original Message-
From: tom [mailto:tomer.d...@intergraph.com]
Sent: November-18-13 1:33 PM
To:
Yes, the upgrade code of the main bundle
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Why-do-i-need-to-add-RelatedBundle-in-the-main-bundle-tp7590702p7590735.html
Sent from the wix-users mailing list archive at Nabble.com.
We tried this
RTM - no related bundle,upgrade code -
{A1245D4C-CFD6-4E43-B2E6-AF6125EF5F8B}
HF1 - related bundle id=A1245D4C-CFD6-4E43-B2E6-AF6125EF5F8B} action =
patch , upgrade code of HF1 bundle -
{CAF25991-D6D6-4FA1-8352-7FA70AB1A720}
HF2 - related bundle
I never used the patch feature, only the add-on feature. So can't help you on
patch behaviour. I also only use the standard BA.
FYI: IIRC, you don't need a detect element in the main bundle if you use the
main bundle upgrade code.
You don't need to use the upgrade code. It can be any
Is there a way to schedule a custom action between two other
custom actions? For example, I have a custom action say CreateUserGroups which
needs to be scheduled after “InstallFiles” but before “WriteRegistryValues”.
Since “Before” and
“After” attributes in the Custom
element are mutually
Greetings one and all, I have a simple question / error I need assistance with.
I'm trying the following
UI Id=UI.Client.UISequence
Property Id=NEXT_DIALOG_NAME Admin=yes Secure=yes Value=Dialog1 /
Publish Dialog=Dialog1 Control=Next Order=1 Property=NEXT_DIALOG_NAME
Hello everyone again,
I'd like to retract and redact my question.
I copied my code AFTER making the property public but the error was when the
property was NextDialogName.
I guess I answered my own question.
Stephen Tunney
Nuance Communications, Inc.
Solutions Architect, Imaging Division
Hello, I try to create a Bootstrapper to install SQL EXPRESS 2012
I have create a custom UI to ask the user to Password and Instancename.
If I put hardcoded the Instancename and Password then it works. But I didn´t
find the correct syntax to use the new Variables. Here are my package
Anyone have any ideas as to find out within a custom action what UI dialog it
is currently executing from? Even the exact control that invoked the DoAction
automatically would be fantastic.
I'm just trying to eliminate having a half-dozen specialized public properties
in several pushbuttons
Hi All,
We were trying to pass the [WixBundleVersion] on to an MSI from Burn:
MsiProperty Name=BUNDLE.VERSION Value=[WixBundleVersion]/
However, when the MSI ran, the commandline showed:
Command Line: MSIFASTINSTALL=7 BUNDLE.VERSION=0.0.0.0
It passed 0.0.0.0 instead of our Bundle/@Version Value.
I don't think there's a built-in way, but you could have a property called
CurrentDialog and set it in an action event just before you call the CA,
and the CA can get the value. Sorry, but I guess that's another property,
and maybe a scheme like this is what you're trying to eliminate.
Phil
On UAC systems a check like the one you have will not always work properly
because Privileged doesn't get set until an MSI elevation prompt which is
after the launch conditions.
That check works when you run from an elevated prompt because that forces
elevation of the entire MSI including the
Classification: Public
Here is what I have for SQL Server Express 2012 however I am installing with
windows authentication but it does work perhaps this will help you?
ExePackage Id=A_SQLExpressx64
DisplayName=Microsoft® SQL Server® 2012 - Express Edition
x64
If the other two are already in the right order, and they aren't numerically
right next to each other, then you can pick either one and use the appropriate
attribute.
After=InstallFiles will pick the next number after the number assigned to
InstallFiles, and Before=WriteRegistryValues will
Thank you for your example.
My problem is not the installation only. I want to use variables for the
instancename and the password. They dont work for me. I dind´t find a way,
to find out what is the InstallCommand, when they try to start the
installation. The logfile have no information about
29 matches
Mail list logo
