Best regards,
Jerry
--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Sel
I have been following this thread and trying to figure out a similar issue
using WcaErrorMessage in my CA and trying to catch the error event and
display a message in my Burn mba. I did not know how similar this was to
your (Soren's) efforts, so I started another thread here:
http://windows-insta
Dit mailadres is niet meer in gebruik. Mail kan je voortaan sturen naar
basti...@careercontrol.nl.
--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+
Hi Phil,
I'll have to look into MsiSetExternalUI() some more. It sounds like exactly
what I'm looking for.
What I meant about the message box in my previous message was just what I
read on MSDN about MsiProcessMessage():
"To display a message box with push buttons or icons, use OR-operators to
ad
This .wxl file is an oddball, being the only one that I see that uses these
UI elements to resize controls from a localization file. Bob Arnson wrote a
blog about it here:
http://www.joyofsetup.com/2012/07/14/localizing-more-than-strings-in-wix-v3-6/
And the bug that led to adding the UI element
MsiProcessMessage (and I assume also the managed WiX equivalent
session.message) is more versatile than just error messages. It will
show information messages, let you manage the progress bar from a CA,
write your own logging into the MSI log etc. You will never see any
strange messageboxes popping
Hi Phil,
Correct me if I'm wrong, but as far as I've been able to tell with
MsiProcessMessage() it doesn't just send a message to the installer; it
actually causes an error dialog to be shown (if you set the error
property). What I would *really* want to achieve here is to catch that
message in my
The only Other thing I see is Possibly this:
Should this not read:
?
Carter
Quoting Janne Rantala :
> Thanks, I've stumbled upon that solution earlier but decided not to use it
> at that time. I'm pretty happy with having two separate msi installers if I
> could only make that Finnish versi
Thanks, I've stumbled upon that solution earlier but decided not to use it
at that time. I'm pretty happy with having two separate msi installers if I
could only make that Finnish version to work. If there won't be any quick
solutions for my problem I'll take another look at that single installer.
I know this is a little off the subject, but are you the original
author of the WiX File? In either case, you need to spend some time
Renaming or at least commenting the code so that people working after
you know what Feature AAA installs. Same with BBB etc.
In some Cases decoding variable
I'd install the patch creating a verbose log, if you've not already
done so, and verify that the values of the other properties in the
expression are as expected. If it's deferred then it must be after
InstallInitialize, so it will be after CostFinalize as required. Your
original post also asked h
Try the Approach documented here:
http://www.installsite.org/pages/en/msi/articles/embeddedlang/
Quoting Janne Rantala :
> Hi,
>
> I've tried creating installer based on WixUI_Mondo dialog set. My setup is
> pretty simple, basically I've just added ui reference to WixUI_Mondo. This
> works very
Found the resolution of my problem, if interesting. If you are making a
bootstrapper, you should override ResolveSource event in your bootstrapper,
like
ResolveSource(object sender, ResolveSourceEventArgs e)
{
if (!string.IsNullOrEmpty(e.DownloadSource))
{
Hi,
I've tried creating installer based on WixUI_Mondo dialog set. My setup is
pretty simple, basically I've just added ui reference to WixUI_Mondo. This
works very nicely until I create localization file with culture fi-FI.
After that I'm getting exception
light.exe(0,0): error LGHT0001: Cannot
Okay do you have a small example of using XmlConfig to create and set the
value of a key, as I was also trying XmlConfig and I did not get any errors,
but it did not do anything to the .config file?
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nab
I have a couple of WIX projects that start install and start services. As I
need the installers to work on non-English machines, I have been using
WixQueryOsWellKnownSID properties to provide localised account names for the
services.
But I have obviously got something wrong; because although th
Ok, i solved the problem myself.
I deleted all Visible="yes" and set the Width on -11 and it works now :)
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-UI-Text-from-Startpage-overlapping-with-text-from-Modifypage-tp7594670p7594728.h
17 matches
Mail list logo
