Mark the Variable and Property both Hidden and they should not be logged.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Kevin Spence [mailto:kspe...@gmail.com]
S
Hi all,
I'm sure this has come up in the past, but I can't seem to find any info
that tackles this scenario.
How do you pass secure information from the bootstrapper to the MSI bundle
without it being logged?
I've seen the articles for burn hidden variables and msi hidden properties,
but nothing
Product.wxs entries
First to define the custom actions
Now to schedule them in the installexecutesequence
REMOVE
REMOVE
And now the custom action code
[CustomAction]
public static ActionResult UninstallMessage(Session session)
{
As soon as I sent out that e-mail, I realized that I haven't tried escaping
the characters in order to embed it withintags. And that worked for me.
Sorry!
Thanks,
Liz
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-hyperlink-in-bal-Codit
Hi,
Within my Bootstrapper Application (using
WixStandardBootstrapperApplication), I use bal:Condition to detect a
pre-requisite and display an error message if it's not installed.
However, as part of the error message, I'd like to also provide a URL to
take the user to the download page. If I p
That might be the detail that makes the difference - messaget types of
error and warning are shown by Session.Message and equivalents, but
perhaps not the ones that resolve to INSTALLMESSAGE_USER.
---
Phil Wilson
On Fri, Mar 21, 2014 at 11:22 AM, Harold Wood (H10 Capital)
wrote:
> I
I setup a custom action that only executes during uninstall, the custom action
code then uses the session.message function with the message type set to
warning. This displays the message text I supply in the record. It works
great! I thank everyone that supplied suggestions, they gave me the d
Good point. In my case, the -arch switch is always being correctly set. That
may make a significant difference.
--
John Merryweather Cooper
Build & Install Engineer – ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry
I also stopped using Win64, but you need to make sure that the -arch flag is
being passed on the command line to candle and light. One way to do this is
to add the InstallerPlatform MSBuild Property to your project file. You can
unload your project file, and edit it, adding the following statemen
So you have compared every single file installed between the InstallShield
install and the WiX install and they're the same?
Same for any registry settings?
I'm not likely to be able to help you, but if you don't tell the WiX-smart
guys here what you've done and what you've found, they're not goi
Depending if you want a Bundle :
[1]http://wixtoolset.org/documentation/manual/v3/xsd/wix/exepackage.htm
l
Or an MSI :
[2]http://wixtoolset.org/documentation/manual/v3/xsd/wix/customaction.h
tml
Le Ven 21 Mars 2014, à 17:56, Hoover, Jacob a écrit :
Burn, running an EXE installer (whi
>From my post in that other forum
I can't tell where or how your CA is being called, but there are two
possible reasons I can think of:
You're calling it from a deferred custom action, and that means you
need to use CustomActionData to get the value.
The property is not marked Secure="yes" t
Burn, running an EXE installer (which may contain a MSI installer) is not
supported. Create a Bundle, and place the exe installer into your chain.
http://msdn.microsoft.com/en-us/library/aa368010(v=vs.85).aspx
-Original Message-
From: Joel Palmer [mailto:jpalmer1...@comcast.net]
Sent:
I'm not sure - I was under the impression that calls that that
ultimately ended up as MsiProcessMessage calls wouldn't show at
uninstall, but by now I'm probably just totally confused :)
---
Phil Wilson
On Fri, Mar 21, 2014 at 9:36 AM, wrote:
> I make small test jscript custom acti
I make small test jscript custom action with Session.Message, and I can see
message box on uninstall. But when I set msi options to disable UI - I can’t
see message box. Where is the problem?
С уважением,
Бетке Сергей Сергеевич.
От: Phil Wilson
Отправлено: пятница, 21 марта 2014
You need to persist the VIRTUAL_DIR_VAL (store it in the registry) so the
uninstaller knows it has changed otherwise it will use the default values.
http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern
-Original Message-
From: Suvrajyoti Panda [mailto:s
I have a prerequisite that must be run before my installer continues. Can
you give me a code example on:
1. How to call the executable. Custom action? Script?
2. How to verify that it ran. Look for a file in a directory?
3. How to pause the install until it is verified.
In the general context of showing messages during MSI activities
session.message (aka MsiProcessMessage) is the correct answer. In the
context of this particular issue of showing a message during uninstall
it isn't the required answer because uninstall shows no UI and
therefore session.message won'
I am stuck with this from quite long now , the ListBox "SETUPLOGLEVEL"
Property is not showing the value in C++ Custom action when I am calling
MsiGetProperty(hInstall, L"SETUPLOGLEVEL", Pid, &PidLength). The pid is
showing 0 value after execution of this function also, I checked by
debugging the
Interesting, I was able to get it to work by simply removing the Win64
attribute altogether. I swear I tried this before and it didn't work...
Just needed a nights sleep I guess.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/util-RegistrySearch-
I do not use the Result attribute, but other than that I do use
Win64=$(var.Win64) for two util:RegistrySearch elements. One returns an
Install Location, and one returns and integer. Both work fine.
The installer/bootstrapper is re-compiled each time depending on whether it is
x64 or x86.
--
http://stackoverflow.com/questions/22559113/utilregistrysearch-registry-key-not-found-when-using-variable-inside-win64
Am I doing something wrong?
Thanks,
-dirt
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/util-RegistrySearch-Registry-key-not-
Hi All,
I am creating virtual directory through WIX installer. The installer
allows user to change the name of the virtual directory through a custom
UI dialogue. The default virtual directory is PFWServiceApplication. If
the user changes this to say PFWServiceApplication_Test then the correct
I didn't try much because when i run the project on Windows 8 using VS,
everything is working fine. I odn't think there is a dependency issue.
In my understanding there may be problem with the way I pulled the
sources(normally ANY CPU, for x86 you get the files from x86 release folder
and the same
You've had a number of suggestions for troubleshooting. Have you followed
them? If so, what did you find? If not,why not?
On Mar 21, 2014 2:29 AM, "karthikrangaraj" wrote:
> To All,
>
> For testing and i made an installer using Install Shield LE and the
> application works perfectly fine on both
Hi Guys, I made asetup file using InstallShield LE and the installer works
perfectly on Windows 8 32/64 bit OS.
Then i used 'WIX Bootstrapper' to combine two installers .exes.
When i launched the .EXE generated by WIX after the accepting the terms and
conditions, I got the error message 'Error rea
it isn’t official note from Microsoft. sample code for jscript custom action:
https://github.com/Metrolog/ITG.NevaTest3303P/blob/master/ITG.BDE_PRO/BDECustomActions.js
For simple message box jscript Session.Message is optimal solution, why not?
С уважением,
Бетке Сергей Сергеевич.
О
Hi,
In my installer am creating DB and running create/alter table scripts.
if any script fails, how can i handle the error from wix?
pls find the below code
*Component Id="cmp39152CBE55BD4B39B74F75CAC45B7B87"
Directory="INSTALLLOCATION" Guid="07B7EF72-F434-46DB-A94A-59C35534651E"
KeyPath ="yes
Hello,We are trying to create a Minor Upgrade for an installer which we created
with the use of wix toolset 3.8. We used SharpDevelop to build the old and the
new version of our installer. Both Product Id and Upgrade Code stay the same.
For now there are only minor differences between the two in
To All,
For testing and i made an installer using Install Shield LE and the
application works perfectly fine on both Windows 8 32/64 bit. There is
nothing wrong with the dependencies.
I may be making some mistakes with WIX or there may be some other problem.
I want to dig more but I need some s
30 matches
Mail list logo
