Hi Jacob,
Can you please explain how it can be done using custom action using C# or
any other language your are comfortable with??
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Domain-Admin-check-in-wix-installer-tp7597895p7597936.html
Sent from
Hi John,
Can you please explain how it can be done with custom action?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Domain-Admin-check-in-wix-installer-tp7597895p7597937.html
Sent from the wix-users mailing list archive at Nabble.com.
Is there a way to **insert** a new XML element at a particular location using
XmlConfig, rather than just adding it?
I am using XmlConfig to register a new IIS handler in applicationHost.config.
Unfortunately, my code ends up adding the new entry at the end of the handler
list, and so the new
What I meant in the previous thread was that, I had conditions set on
components and these were not getting evaluated when the msi was run in
maintenance mode. Fiddling with Transitive, RemoveFile, KeyPath, didn't seem
to help. The components installed fine during fresh install.
Per your sugges
I'm using the WixStdBA to conditionally install either a 32-bit or a 64-bit
MsiPackage.
When my 64-bit package is installed a 32-bit version of msiexec.exe is launched.
Is there way to force the 64-bit msiexec.exe to get launched?
My MSI has a custom action to check for a running process and v
Thanks Sean! All I had to do was define the new Font in the RTFTheme.xml.
-Original Message-
From: Sean Hall [mailto:r.sean.h...@gmail.com]
Sent: Thursday, November 6, 2014 6:47 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] FontId descriptions
The FontId refer
OK I figured out the issues. A Transform is not required, however until I
provided a path to a Transform file it would just skip the HarvestDirectory
target. Once the path to the Transform (bogus as it was) was provided, it
launched heat, which provided error (0,0) and printed the full path to th
Well it seems that a path to a Transform file must be provided. I provided a
path and now heat is launched. Still not working as it is a bogus path, but
I can refine that further. Curiously I don't think that I used a path to
the transform when the project was building a few days ago, as I have
What does "Any thoughts on why the conditions are not evaluated correctly in
Maintenance mode?" mean? Are you saying that this scenario is not a
fresh install to a clean system?
It's more common to use features as containers if you allow these to
be added or removed at install and during maintenan
I have used HeatDirectory Tasks in several projects by creating a custom
Target and adding it to the BeforeBuild DependsOnTargets list. But now I am
trying to understand how to user the HarvestDirectory target. I added code
like this to a wixproj file.
INSTALLFOLDER
EDSsetupG
Attachments don't come through. Either post a link to a sharring location or
post the text.
This is an area I have not worked with for a long time, so maybe someone
else sees the issue. Is the issue related to the fact that the KeyPath is
not on the File? Does your RemoveFile on='both' element
Please find attached log of maintenance mode.
Since the target file name is the same, I am also including a in
the Component like this -
I have the property defined as
And the Radiobutton control is
I think a more complete log would be helpful.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RadioButton-property-not-evaluating-correctly-in-Components-Condition-tp7597915p7597922.html
Sent from the wix-users mailing list archive at Nabble.com.
Thanks Phill for your quick response. Appreciate it!
Including the Transitive="yes" to the components doesn't seem to change the
behavior in Maintenance mode. The Components are not marked to install.
Is the condition in using the Radio button property, incorrect by any change
?
I do see in the
MSI conditions are only evaluated for initial install of a Feature, unless
you mark the component as transitive.
http://msdn.microsoft.com/en-us/library/aa372462(v=vs.85).aspx
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RadioButton-property-no
There is a feature request for this.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Mohamed Yasir [mailto:yasirmohame...@gmail.com]
Sent: Thursday, November 13, 2014 3:10 A
Your custom BA can move the log files. It is provided the paths to all of them.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Partyka, Rouslan [mailto:rouslan.part...@contr
Hi,
Can I not use property set in Radio button group to conditionally install
a component? I am unable to correctly evaluate conditions in a component.
I have 3 Radio buttons with Values 1, 2, 3. A Secured property named
UNICODETYPE is defined in their RadioButtonGroup.
I want to install diff
Script based ca's are unreliable at best. Odds are your vbs script is failing
on uninstall.
Logs would verify this, and you can use orca to condition the script not to run
on uninstall. From there you should be able to uninstall the existing installs
(you may have to tell windows installer to r
Yes it's right !
This is the modification :
NOT
Installed AND NOT REMOVE
Thanks you for your help.
Fabrice
-Message d'origine-
De : Renan Lefeuvre [mailto:r.lefeu...@ag2l.fr]
Envoyé : jeudi 13 novembre 2014 16:21
À : General discussion about the WiX tool
Hello,
I think that it is your vbs which causes the problem because it's excuted on
install and uninstall.
Maybe you could add a condition to execute your custom action.
Regards,
Renan
-Message d'origine-
De : Fabrice MAUPIN [mailto:fmau...@iback.fr]
Envoyé : jeudi 13 novembre 2014 1
Hi everybody,
When I try to uninstall my application, this message appears :
There is a problem with this Windows Installer Package.
A script required for this install to complete could not be run.
Contact your support personnel or package vendor.
For information my application is
I surely did. And I also had my WTF moment with those
(null)_0_MSI_PACKAGE_ID.(null) files. Just wasn't sure.
So it's a bug after all. OK then.
Phill Hogland wrote
> Did you review this thread?
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Disable-logging-in-Burn-td759746
The application should be doing the security, not the installer. Anyone with a
little knowledge of MSI could use orca and remove any CA you put in.
It may stop an honest user.
Sent from my iPhone
> On Nov 13, 2014, at 8:01 AM, "John Cooper" wrote:
>
> Yes, with a custom action.
>
> --
> John
Yes, with a custom action.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: Sourabh Bhandari [mailto:sourab
I don't think the chain sequence can be changed, but the following thread
proposes using a RelatedBundle to achieve a similar goal.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Change-MSI-Package-Install-Uninstall-Order-tp7597904p7597907.html
S
Why? By design the chain is always in reverse order when uninstalling.
> On Nov 13, 2014, at 7:37 AM, "Saravanan" wrote:
>
> Hi All,
>
> I am using Wix 3.9. Created installer using custom Boostrapper application.
> I need some clarification about MSIPackage execution sequence.
>
> My Bundle\C
Hi All,
I am using Wix 3.9. Created installer using custom Boostrapper application.
I need some clarification about MSIPackage execution sequence.
My Bundle\Chain having,
On Installation, MSI installed in following sequence,
SamplePackage1.msi
Sampl
For what it's worth, I recently proposed adding this to WixStdBA, but we
haven't had time yet to discuss it.
> On Nov 13, 2014, at 3:27 AM, "CALCEL Sebastien"
> wrote:
>
> Thanks for your answer Jacob.
> I ended on same conclusion about the custom BA.
>
> -Message d'origine-
> De : H
Use the ExePackage/@InstallCommand, but the specific flag depends on the
design of the exe.
Did you mean to use a /q or a -q rather than \q? I don't think I have ever
seen \q used before. The vendor of the exe package should provide the
correct syntax for that package.
--
View this message in
Not sure I understand, but if you want to modify MsiPackage/@DownloadUrl at
runtime, you can do that in your ResolveSource handler. The package at the
URL you specify must be the exact same package as was available to Burn when
the setup was compiled or you will get hash failures. There is a 1:1
Did you review this thread?
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Disable-logging-in-Burn-td7597469.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LogPathVariable-not-working-tp7597897p7597901.html
Sent from the wix-u
Yes the LCIDs are used in the WiX context for wxl files, but in the .Net
context of the managed BA two letter culture or culture-Region tags are
used.
I think that there are two areas where issues are likely.
1) Validating that your DLL is at the path from which the app is trying to
load it. Use
Hi,
I am using Wix toolset 3.8. I have created custom bootstrapper application
for creating web installer setup.
It downloads MSI file from online.In Default,downloaded MSI was stored in
%programdata%\Package Cache location.
Is there any way to change the default download location of msi?
Can
Hi,
While using the "DisplayInternalUI=no" attribute of MsiPackage element in
bundle, we can achieve silent installation of an msi. Like this, is there
any attribute for ExePackage we can use for silent installation ?
I'd used "InstallCommand=\q" attributes of ExePackage, but still no use.
Silent
Hello,
I have a bundle with 3 chained MSI's. I want it to put all (!) the log
files to a specified folder, and I don't want to use the command line (i.e.
it has to be hardcoded in my .wxs).
Does anyone have a code sample that actually WORKS? I checked the web, I
tried LogPathVariable, and in
Thanks for your answer Jacob.
I ended on same conclusion about the custom BA.
-Message d'origine-
De : Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Envoyé : jeudi 6 novembre 2014 15:53
À : General discussion about the WiX toolset.
Cc : FAURE Helian
Objet : Re: [WiX-users] Major Upgra
Hi wix-users..
Is there any way to check whether user is domain admin on Active Directory with
wix (expecially in wix 3.9).
Let's say we have group X which is sub-group under group 'Domain Admins', so
any user who is member of group X automatically becomes domain admin.
Basically I want to make
38 matches
Mail list logo
