I find it more elegant to have the custom action only set a property and
return. Then on the remaining control events use the property in a
condition to perform a SpawnDialog on a custom dialog that displayes the
error message. This way MSI continues to handle the UI.
--
I have this wix code that calls a VBScript code to show a window:
Not Installed
The window is shown but it's hidden under the wizard window.
How can I bring it to the front, or else side of the wizard window?
Kuro
-
> If the driver is not signed, and you say it is not, then you need the Legacy
> option. I did say that; what I meant was "not signed with a certificate from
> a CA." It is self-signed at the moment. Apologies for the confusion.
I'd still like to hear if anyone has any comments on a per-user inst
Thanks for the quick response Chris.
My issue is that the keys are NEVER copied into HKCU on XP or Win 7 64bit.
I would love to see a working example though if you don't mind.
Thanks again.
Jon
From: Christopher Painter [mailto:chr...@iswix.com]
Sent: Tuesday, January 17, 2012 4:16 PM
To: McCai
ActiveSetup predates MSI and doens't really know anything about MSI. The
only thing that ActiveSetup "copies" is the version registry value so that
it knows it doesn't need to run again. What active setup really does is
run a program. This program could be Notepad but in our case it's msiexe
Okay last question here...
Does Active Setup require that some component be set as ADVERTISED?
I have not been able to see Active Setup copy ANYTHING from HKLM to HKCU for
the non-installing user.
There has got to be a way to get this to work that I am just blindly not seeing.
Jon
-Origin
I'm adding a new file to my MSI. I've created a new component for it in the
MSI and included it in the patch.wxs. When I look at the patch via orca, it
looks like the file is there and fine.
However, when I apply the patch, I get the following error in the log.
DEBUG: Error 2247: Database:
In the ServiceControl element that starts your service, what's your Wait value?
It's not documented in MSDN, but AFAIK a Wait value of 1 causes a wait for the
Service to start successfully and if it fails the install will roll back.
Phil W
-Original Message-
From: Jeremy Farrell [mail
I've created a 2 custom action:
1. TestReportServerUrl
2. PublishReports (deffered)
both establish a ReportService2005 instance and then sets the URL and
Credentials (username, password and domain) captured using custom dialog.
[CustomAction]
public static ActionResult TestReportSe
"The driver will be signed for production; it just isn't at the moment"
It doesn't matter what will eventually be done. What matters is that your
driver is not currently signed. The Legacy option / Windows can't see into
the future and know that you're eventually going to sign it.
"I shouldn't
Define the properties that you want passed to your MSI using
elements under the corresponding element. You can set the
MsiProperty@Value attribute to the value of a element. Your BA
can change / update the value of the Burn variable.
So here's a burn variable that you will later set through you
You can try writing your URL file from the IniFile table instead, as .URL
files are in INI format. I am going to try exactly this later on today,
I've done it before (but not in WiX) so it should work. I'll post my
sample code if you need me to.
Regards,
Dan
On Sun, Jan 15, 2012 at 4:32 AM, Bob
Thanks, although I have it working now without setting the
SelectionLanguage, I did try that out when debugging. I assume they are
very similar if my XPath pattern match works as expected even when parsed
as XSLPattern.
On Sat, Jan 14, 2012 at 3:20 AM, Blair wrote:
> In your XmlFile elements ma
Unfortunately MSI UI doesn't natively support an Open File Dialog. So, yeah,
you'll need a custom action to display one.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Is-there-a-UI-Control-to-pick-an-existing-file-tp7195026p7196469.html
Sent from t
Hi,
Can someone help whit this :
Referencing a merge module which creates a database:
Fls.Xxx.Install.msi content:
Line 58
Fls.Xxx.Config.Module.msm content:
http://schemas.microsoft.com/wix/2006/wi";
xmlns:sql="http://schemas.microsoft.com/wix/SqlExtension";
RequiredVersion=
Hi Romeo,
it's quite simple:
The bootstrapper will probably start "msiexec /i installer.msi",
right? Simply append TARGETDIR="InstallLocation" to it and you're
done.
For any other property, you can do the same: make the property public
by writing it all uppercase inside your wxs files, assign a r
16 matches
Mail list logo
