Hi,
I have some problems with using the new burn feature. I want to create
a bootstrapper that checks for a particular .NET version and then
eventually installs the missing prerequisite before it installs my own
application.
If have two problems:
(1) The DetectCondition for my .NET
Dear all,
I believe this is a bug in wix 3.6, but not sure...
If I do the following :
Property Id=SQLCMDPATH
RegistrySearch Id=SqlBinsRegistry Root=HKLM
Key=SOFTWARE\Microsoft\Microsoft SQL Server\100\Tools\ClientSetup
Type=directory Name=Path
FileSearch Name=SQLCMD.EXE /
I am making my installer.
I need to run another foreign installer in it.
I am making this -
---
InstallExecuteSequence
Custom Action=QtE1 After=InstallFiles /
/InstallExecuteSequence
CustomAction Id=QtE1 FileKey=SETUP.EXE Execute=immediate
Sorry,
I accidently sent this mail a second time. :-(
Just ignore it.
Regards,
Mathias
On 07.11.2011 09:57, Mathias Bauer wrote:
Hi,
I have some problems with using the new burn feature. I want to create
a bootstrapper that checks for a particular .NET version and then
eventually installs
Hi,
I've created a WIX project in my solution that works as expected,
especially it rebuilds only if one of the projects it depends on changes.
Now I've added the C++ runtime as a merge module, and now the WIX
project is rebuilt every time I build the solution.
Here's what I added to my
On 03.11.2011 02:18, Bob Arnson wrote:
On 02-Nov-11 07:55, Mathias Bauer wrote:
[0BBC:11CC][2011-11-02T12:47:18]: Setting string variable
'DotNet30InstallRegValue' to value '1'
[0BBC:11CC][2011-11-02T12:47:18]: Setting string variable 'DotNet30Version'
to value '3.0.30729.5420'
Is Wix, Burn and Votive 3.6 compatible with the VS2010 service pack? I don't
want to upgrade to service pack 1 if there is a problem.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Votive-compatible-with-VS2010-SP1-tp6970417p6970417.html
Sent from
Running an installer from within an installer is not supported. The msiexec
processes that are already running are going to block the inner install. To
achieve the effect of what you want, you'll need to use a chaining bootstrapper
like burn, DotNetInstaller, or something similar.
--
John
I use Votive in WiX v3.5 with VS2010 SP1 without any issues. I would assume
Votive in WiX v3.6 follows suit. No idea about Burn, haven't had time to look
into using it yet.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
Old bug with FileSearch which has been closed but never actually fixed as far
as I can see -
http://sourceforge.net/tracker/?func=detailatid=642714aid=1648267group_id=105970
http://sourceforge.net/tracker/index.php?func=detailaid=1273447group_id=105970atid=642714
Palbinder Sandher
Software
I use Votive with Sp1 no problems. In fact, having migrated from 3.5 a few
months ago, I think 3.6 is more stable.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Monday, November 07, 2011 8:28 AM
To: General discussion for Windows Installer XML toolset.
Unless they've been worked out in the Beta, there can be build order issues
when running 3.6 builds on build agents. I haven't had an opportunity to test
3.6 recently (too close to the end of the release cycle) to know if it's fixed
yet.
--
John Merryweather Cooper
Jack Henry Associates,
I can say with confidence that it is fixed in [at least] build 3.6.2207.0.
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Monday, November 07, 2011 9:34 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Votive compatible
I'm using VS2010 and Wix for 2 weeks for now, and did not have any issue with
them.
Regards,
Nicolas Penin
-Message d'origine-
De : David L. Beckwith [mailto:beckw...@interaccess.com]
Envoyé : lundi 7 novembre 2011 14:53
À : wix-users@lists.sourceforge.net
Objet : [WiX-users] Votive
I've tried to install WiX 3.6 beta on VM with Server 2008 on it and
I've had a failure to install.
The VM also has SQL server 2008R2 on it which means it has that
partial Visual studio install that Management studio gives you but
otherwise it's fairly plain with .net 3.5SP1 and 4.0 installed.
The permissions are:
SYSTEM: Full Control
Installer Service Account: Full Control
So no other users can access or execute the shortcut. I can see only two places
in the log file where file security is set and that is when calling the system
restore service before installation
Thanks - you were right, just signing the native CA was sufficient !
Deepa
On Sat, Nov 5, 2011 at 12:54 PM, Christopher Painter chr...@iswix.comwrote:
I'm wondering where this requirement comes from. If the Native CA is
signed, why does it matter in an assembly that is stored inside of it is
Would it be of value to call out on the Property attribute on an
InstanceTransforms element that it must be a property that is defined in
the Property table? Simply adding Property Id=INSTANCEFOLDER
Secure=yes/ and then referencing this property will cause the
transform to be invalid. In order
And most Windows Installer paths end with a \ too, in the path properties.
Phil Wilson
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Monday, November 07, 2011 6:45 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
Am 06.11.2011 19:18, schrieb Harper:
As far as I remember correctly, one advantage of Votive was the simple
integration of other projects output to a WiX project. Am I wrong here? What
does the Harvesting group in the Reference properties means?
Current settings: Harvest=True,
I'm sorry this is off-topic, but I'm having a hard time finding a download
location for the latest Windows Installer SDK. All of the links on
Microsoft.com are wrong. There is a lot of info, but no actual download
location.
Can anyone give me a link or at least an explanation of why this
It's pretty easy.
Install the package, you should see a new project type tab that includes
setup projects, merge modules and libraries. What you end up with is a shell
Xml file that works just like it would without Votive.
You can add a project reference and then use something like this:
Okay, I see that the platform SDK installs it in the bin directory. Since
there's nothing in the installer UI that specifically mentions the Installer
SDK, I didn't think it was there.
I'm sorry for the OT message.
Jamie
From: Jamie Hankins
Sent: Monday, 07 November, 2011 13:16
To:
Hi,
I have a Wix project, that should create a installer that can be
installed either with UI or without UI. So I want to make sure that a
property gets set either from the command line or the UI otherwise the
installer should abort with a message like Property PROPRERTYNAME must
be set,
One would think a simple condition within the InstallExecute table could
then trigger a custom action.
Ex:
CustomAction Id=CA_BlockPropertyNotSet
Error=!(loc.LaunchCondition_PropertyNotSet) /
InstallExecute
Custom Action='BlockPropertyNotSet' After=FindRelatedProductsNOT
I'll try this, thank you for your suggestion. Just to understand your
example shouldn't the InstallExecute Sequence be this way:
InstallExecute
Custom Action='**CA_BlockPropertyNotSet**' After=FindRelatedProductsNOT
PROPERTYTHATMUSTBESET/Custom
/InstallExecute
instead of this:
The WiX documentation for the CustomAction element already says what the Error
attribute is for:
http://wix.sourceforge.net/manual-wix3/wix_xsd_customaction.htm
That page even includes a link to the Custom Action Types page in the Windows
Installer documentation that describes what a type 19
Yeah, brain fart on tying the custom action to the Custom Id.
-Original Message-
From: Robert Brunhuber [mailto:w...@rbrunhuber.de]
Sent: Monday, November 07, 2011 3:44 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Ensure that a property is set in setup with UI
I am trying to create a patch install (.msp). It has been a learning
struggle, but I got to the point where the msp install updates some files
(if I use an 'a' flag on reinstallmode). However, in the original wix
project I use paraffin to create a fragment for a database update component.
While
Thank you, for this great hint. I guess it was my mistake to ignore
CustomActions because I did not understand how broad custom actions can
be used. I really thought custom actions mean I write custom, error
prone code and everything is bad ;-).
Thanks again,
Robert
On 07.11.2011 22:59,
John, thanks for reply.
The objective for asking for a tutorial wasn't the starting point and
that it isn't so difficult. I am more interested in exploring all the
features of Votive, especially the harvesting feature. That's the point
where I have found problems.
Does harvesting did not work
My second installer is not MSI installer, it is old VisualBasic Installer
that can run parallely with my MSI.
So the sollution is not in that.
--
View this message in context:
32 matches
Mail list logo
