HI,
Thanks for your help.
It worked for me, Thanks a lot.
-Original Message-
From: Bala [mailto:balakrish...@ameexusa.com]
Sent: 05 November 2014 01:19
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Incorrect syntax near 'DATABASE' while Uninstalling
from
Hi
While reading source code for WiX Extended Bootstrapper Application, I'm
wondering if I want to replace this Theme manipulation (xml based) with
Win-Forms or MFC based UI, do I have to modify/rewrite all that or I can
simply use references of some library, just as in case of Managed
Regarding using BAFunctions.dll for DelayStart, it has been about a year
since I used that feature and then abandoned that code in favor of creating
a WPF managed BA (which I would also recommend, but you could use any UX
framework - MFC, WCF, Java?smile/). But as I recall the basic steps are:
1)
Great! I'll go with option one then. Thanks!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-msi-tp7597706p7597756.html
Sent from the wix-users mailing list archive at Nabble.com.
Hi,
Is there the possibility to launch both install and uninstall actions on
different packages during one bootstrapper run?
I use the following code to launch the actions:
The declaration of the commands I use:
this.InstallCommand = new DelegateCommand(() =
I am trying to alter one of the built in UI's, WixUI_Advanced, and running
into issues with Duplicate symbols.
What I have done:
1. Copied the Fragment contents of WixUI_Advanced.wxs to be local to
my installer project. Saved in separate wxs file
2. Renamed the UI, made the
Hi,
Is there anyone that has created a database using SQL scripts?
I have a requirement to complete this installer and I can't get the database
created.
Thanks,
Gary
--
View this message in context:
From your log:
1) is 'SqlComponent' being selected for install?
If so,
2) What is the value of the property USEINTEGRATEDSECURITY from the verbose log?
Note that this property is going to have to be remembered for repair, upgrade,
and patching to work. Note also that it will currently only
I have created an Installer which writes Registry Values to enable Chrome
Extension (HKLM\Software\Google\Chrome). Till now, everything seemed fine.
Recently, we found out that using 64 bit Chrome on a 64 bit machine will not
enable the Extension after install and it only writes to the Wow6432
I have a product with a similar requirement (it installs extensions to MS
Office in both 32-bit and 64-bit flavors). From a 32-bit install, you can ONLY
write 32-bit registry entries. I work around this issue using a Burn
bootstrapper that installs the 32-bit support with the product, and
Hello,
I am trying to include a DirectX9 install from within my perUser MSI.
Everything works, however I am down to possible elevated permissions that
need to be accessed for the DirectX portion even though I have declared
InstallScope=perUser. I have a feeling that the DirectX installation
What are you wanting to uninstall? Is it an upgrade scenario? Are you trying
to replace an older version of your software with a newer version?
Or are you trying to remove some other software when yours is installed?
--
View this message in context:
Did you update your UIRef element to point to your new UI_Custom?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/FW-Correct-method-for-modifying-a-built-in-UI-tp7597759p7597765.html
Sent from the wix-users mailing list archive at Nabble.com.
Forgot to mention that, but yes.
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Wednesday, November 5, 2014 2:55 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] FW: Correct method for modifying a built-in UI?
Did you update your UIRef element
I don't think the Exit dialog is going to be shown, in most cases, during an
uninstall because Add/Remove Programs (Programs and Features) suppresses the
UI when the user uninstalls from there. So, setting the property directly
may be enough.
I can't recall of the top of my head what that
I didn't read carefully enough. You only want to display the message on
uninstall. Because ARP suppresses the UI, the dialog won't be shown on
uninstall.
I was so close to having this work by simply adding something like that to
Burn's License UI theme. Alas, even though, with Burn, that Exit
Hmm...
Just to double-check:
Copied the Fragment contents of WixUI_Advanced.wxs to be local to
my installer project. Saved in separate wxs file
2. Renamed the UI, made the modifications I needed
---* Did you change the Id on the UI element?*
3. Copied the
Responses in line below
Also want to mention that I am now building these modifications into a
wixlib, though I got the same errors when it was all part of the installer
build.
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Wednesday, November 5, 2014 3:22 PM
The NetFxExtension always downloads it. To have the .NET 4.5.1 package
compressed inside your bundle, you would have to write the mark-up yourself.
You can use how the WiX team did it as a rough guide:
http://wix.codeplex.com/SourceControl/latest#src/ext/NetFxExtension/wixlib/NetFx451.wxs
Also, I have used both v3.8 and v3.9 while trying to resolve this.
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Wednesday, November 5, 2014 3:22 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] FW: Correct method for modifying a built-in UI?
Is SQL Server already set up? When you set it up you can enable Windows
authentication at that point. Otherwise, you'd have to turn it on somehow
during your installation, but could be trickier.
Are you installing SQL Server along with your website install? If so, turn
Windows authentication on
Not sure. Now that you've moved code into a wixlib, any UIRef elements left
hanging around still pointing to the old UI? It's probably something simple
that I'm not thinking of.
--
View this message in context:
Is the install log showing anything helpful? You say it's a permissions
issue.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-DirectX9-Components-within-a-perUser-MSI-tp7597763p7597775.html
Sent from the wix-users mailing list archive
Advanced and Mondo UI's are notorious difficult to modify. They include stuff
from all over. You'll need to track down all those includes (and probably
modify private copies) to get it to work. The only UI's I've regularly
modified are InstallDir and FeatureTree.
That being said, the
Well, last night I thought for sure it has to be a rogue UIRef somewhere in
my script, but as of yet I have not been able to find one.
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Wednesday, November 5, 2014 3:50 PM
To: wix-users@lists.sourceforge.net
As an additional note, my UIs regularly reside within a wixlib with no issues.
If you can get it to work, you can get it into a wixlib no problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® |
I am currently trying a solution of bringing all the dialogs from the source
I need into my wixlib, and not linking against WixUIExtension. Pretty
close, but I need to figure out how to get a hold of uica.dll (without
having to build the entire wix source tree) that is pulled in from
If you're essentially replicating the UI extension, you can use dark to get the
bits you need. But I have not found it necessary to do that with my custom UI
(I still manage to link to the UI extension).
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
I'm suggesting it is a permissions issue because it works on my machine with
elevated permissions. The problem is on a PC that is limited.
I checked the log on the problem PC and get this:
Product: MYProduct -- Error 1721. There is a problem with this Windows
Installer package. A program
You won't be able to force a 3rd party installer to change scope very easily,
especially in the case of an EXE based installation (nor would I recommend
doing so). What exactly are you trying to do? If DirectX is a prerequisite
to your software, use burn to install it in the chain before
Would you happen to have an example of what you are doing that you could
post? I have previously done this with success, but there is something
about the dialogs being published in the Advanced UI that makes then so they
cannot be reused? Before I modified both the flow and a few dialogs for the
I have no story for Advanced, and my attempt about two years ago with Mondo
ended in frustration. I'm not developing further custom UI as I am actively
developing my own managed bootstrapper application to take its place.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise
Yes, DirectX9 is a prerequisite to my app.
I suppose I'm down to 1 option other than having end users installing
DirectX9 themselves.
How do I go about changing my code to include your burn option?
Regards,
Paul
*** Email Confidentiality Notice ***
-Original Message-
From: Hoover,
Another question: If I do something like the following:
UI Id=Custom
Property Id=WixUI_Mode Value=Custom /
/UI
I will get the following error:
: error LGHT0091 : Duplicate symbol 'Property:WixUI_Mode' found. This
typically means
that an Id is duplicated. Check to make sure all your
As mentioned by Jeremiahf, you need to managed your Upgrade scenarios using
Upgrade element in your Wix for your msi.
In your case, you may need to do a major upgrade.
Also, please check if you are not changing Product GUID in your next
upgraded wix.
--
View this message in context:
35 matches
Mail list logo
