Do a search/replace on the generated components wix or use an xslt to
transform it into payloads if it's something you will need to do repeatedly,
in fact you can pass an xslt to heat to transform it for you.
-Original Message-
From: nianderneves [mailto:niander.ne...@gmail.com]
Sent: 25
What Jacob suggests works, we have been using it for several years, if the
certificate is in the original msi and it and the patch are signed by the
same certificate then you do not need to elevate to install.
It's fun when the certificate expires though as you need to use a hotfix to
deliver the
not coming.
Regards,
Srinivas.
On Wed, Jun 26, 2013 at 2:01 PM, David Watson wrote:
> What Jacob suggests works, we have been using it for several years, if
> the certificate is in the original msi and it and the patch are signed
> by the same certificate then you do not need to el
Wesley
I filled in the unsubscribe form on the website for you, you need to reply to
that email (not this one) and you will be unsubscribed.
Dave
-Original Message-
From: Wesley Wells [mailto:wwe...@midsouthmetalsupply.com]
Sent: 27 June 2013 17:00
To: 'General discussion for Windows In
Generally people fix the issue and release a later build version, so your
scenario is quite odd.
If you can't do that you could take the msi with build 3698 in it and edit it
so that it does a major upgrade* (one that uninstalls and reinstalls) with
orca or insted (you may need to re-sign it after
It should come up as unsigned in the UAC prompt, if you have that disabled
you won't see anything. You can usually still install it.
-Original Message-
From: Ivo Beltchev [mailto:i...@ibeltchev.com]
Sent: 07 July 2013 23:34
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Authenti
Does it work if you remove the PatchCertificates elements?
I.e. is insignia hand holding you and doing everything so you do not need to?
-Original Message-
From: Georg von Kries [mailto:g...@creativbox.net]
Sent: 08 July 2013 15:54
To: 'General discussion for Windows Installer XML tool
Merge modules are only really of use these days to share components with
other installation technology.
If you are totally wix based use wixlibs or wix fragments.
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 11 July 2013 13:48
To: General discussion fo
Votive has been part of the standard wix install for a while. If you have
installed 3.7 you should have wix templates (etc.) available in visual
studio.
There should be a "windows Installer Xml" template group if you do file->new
project.
If not try a repair.
-Original Message-
From: Har
Also you could use the Directory or DirectoryRef @FileSource attribute to
say where all files in a folder are pulled in from then you can make your
component definitions very clean.
e.g. your example component would be :-
More components.
This does change the component ID to 'Schedul
Don't you run it with the /layout parameter to download everything you need
locally then copy that to the other machine.
(Never tried it mind).
-Original Message-
From: Philip Mitchell [mailto:mitch...@trdeo.co.uk]
Sent: 18 July 2013 12:17
To: wix-users@lists.sourceforge.net
Subject: [Wi
What error?
-Original Message-
From: Pasquale Fersini [mailto:basquale.fers...@gmail.com]
Sent: 25 July 2013 14:42
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Error launching bootstrapper
Hi all,
on a user machine (Windows XP SP3) our setup, compiled wi
Hi,
We have been shipping with our own (non-burn) chainer packages for years and
not had any problems with these scenarios. In my experience if a
mass-deployment system is being used the end users machines are locked down
so they can't install software by hand so they could not use an .exe to
ins
I don't think burn currently supports this kind of scenario well (it may but
I am not an expert).
What you could do is make a per-user burn bundle that just installs your msi
silently then add that as an .exe package to your main with-prerequisites
bundle.
Or indeed leave it the way you have it a
Isn't the win64 setting on the component so you need to build a 64bit and a
32 bit version of each merge module (or wixlib).
This is easily done with a shared .wxs file and a compilation setting.
I have 32 and 64 bit components all up my build tree just because one package
needs a 32 and a 64 bit
it is built twice once for x86 and once for x64 and
> placed in different folders wixlib/wixlibx64 (both merge modules and
> wixlibs)
>
> So I have 1 MergeModule project / 1 wixlib project but multiple
> configurations to handle the x86/x64
>
> Looks like I am pooched...
mes 10-20 files...
Was able to change 3 other installers from 2 solutions down to 1 solution and
able to create x86 and x64 MSI's
Might just leave this one alone :(
Steve
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: July-31-13 12:08 PM
To: General discussion for W
You need to update the file version to allow windows installer to know
whether or not to overwrite any existing file.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368599(v=vs.85).asp
x
I don't think the string version is used but I always keep them both in sync
anyway.
Windows install
This is now a bug in product1. It needs fixing at a priority that your
product owner decides. You must have an update strategy for that product,
what if it has a critical security issue/flaw?
You could release product2 as a burn bundle and include a fix in it for
product1 by adding a major upgrade
discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Adding a new dependent file to shared component
without breaking component rules
I agree. A common shared component has been updated and it needs fixing in
all the products because it can no longer be shared properly.
Ph
The latter behaviour is automatic, only installed features are patched.
-Original Message-
From: Swaroop Kare [mailto:swaroop.k...@ifdspercana.com]
Sent: 14 August 2013 10:12
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom installation in Wix Patch
In the wix major upgrad
I think -suid manages clashing ids if you only have one pass but not if you
run heat multitple times to generate fragments.
Dave
-Original Message-
From: jo...@msli.com [mailto:jo...@msli.com]
Sent: 16 August 2013 09:29
To: General discussion for Windows Installer XML toolset.
Subject: R
Make a minor update msi that fixes the issue and get your users (or write a
stub that) runs it from the command line with the repair and recache msi
options.
msiexec /fv your.msi /l*v log.txt
-Original Message-
From: John Ludlow [mailto:john.ludlow...@gmail.com]
Sent: 28 August 2013 1
I don't think there are issues with re-distributing the wix toolset as I have
seen third party tools do that.
Double check the license.
I would personally just link to the site with instructions or if needed
distribute the entire toolset.
Dave
-Original Message-
From: biswajitbiee [mailto
You can host your ui in the bootstrapper ask all the questions, then install
sqlexpress if needed then run your msi with relevant properties to install the
services/populate the database.
Dave
-Original Message-
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: 09 Septembe
You don't.
You have to change the maintenance mode UI to be what you want.
-Original Message-
From: dileep s [mailto:dileep.sanamp...@gmail.com]
Sent: 10 September 2013 12:44
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] [WIX] How to installing same MSI f
The evaluation order of launch conditions cannot be guaranteed.
Also they are conditions on which to launch the msi so if the condition is true
the message is NOT displayed.
I can't see your conditions to see if that is an issue for you.
If any launch conditions fail the rest of the conditions
The windows installer property reference is a good resource to know.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370905(v=vs.85).aspx
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: 11 October 2013 17:10
To: General discussion for Windows Install
Check out this
http://stackoverflow.com/questions/3560370/custom-action-in-c-sharp-used-via-wix-fails-with-error-1154
Why are you not using the service control element to ensure the service is
stopped?
http://wixtoolset.org/documentation/manual/v3/xsd%5Cwix%5Cservicecontrol.html
-Original
Create a 0kb placeholder files in your empty directories, if you want them to
be included automatically.
Would be an interesting addition to heat to allow empty folder harvesting.
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: 25 October 2013 10:43
To: Genera
working fine.it is
creating empty folders.
On 25-10-2013 16:22, David Watson wrote:
> Create a 0kb placeholder files in your empty directories, if you want them to
> be included automatically.
>
> Would be an interesting addition to heat to allow empty folder harvesting.
>
If you mean to share files between two different product MSIs then you need to
author them carefully to make sure that they share the same component guids.
-Original Message-
From: Daniyyel [mailto:daniel.bed...@freenet.de]
Sent: 15 November 2013 12:09
To: wix-users@lists.sourceforge.ne
Anything that is customizable is regarded as user data and should be installed
to a safe non-live location and then copied to the live location during your
programs first run configuration step (or post install custom action).
Your confg tool/CA then knows where the template source is (which is
They are right, burn is a tool to allow you to collect data and chain some MSIs
silently, but you will need to make a custom BA to get the most from it.
The visual studio installer is a custom burn BA that does just that.
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
allUISequence
> > 2-3 lUI.wxs (based off of a slightly modified WixUI_FeatureTree
> > pattern)
> >
> > Haven't decided where I'll define my properties. Maybe a
> > Properties.wxs or (more likely) in the UI.wxs files since that's
> > where most of t
Its 0x0800 in CustomAction.Type
-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com]
Sent: 03 December 2013 12:43
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Deferred vs.
elevation
Thanks.
What flag/option get set in Windows Installer tables whe
The easiest and cleanest way is to make the daily builds update the build
number (third part of the msi product version) each build and implement major
upgrade with a * product code (if you don't already)? Then dev builds always
install and remove any previous build.
You alter the product code
If you are not shipping the simulator and it is already on the target machine
you can use a directory/file search to search the hard disk for it then use the
resulting property to set the registry value.
See
http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/parentdirectory
The wix properties are populated by an api call at runtime, so it should be
working fine and they are the correct option in this case.
There may be a specific issue in this language.
Is there anything interesting in the install log?
-Original Message-
From: Stephen I. Woolhead [mail
s and see if they work.
Cheers,
Stephen.
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: 16 January 2014 16:42
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problem with service install on non English OS
The wix propertie
e log file, you can see a bunch of errors starting around line 9319 as our
custom actions attempts to start the services.
Cheers,
Stephen.
-Original Message-----
From: David Watson [mailto:dwat...@sdl.com]
Sent: 17 January 2014 09:29
To: General discussion about the WiX toolset.
Subject: Re:
To unsubscribe to this mailing list go to...
https://lists.sourceforge.net/lists/listinfo/wix-users
-Original Message-
From: Milagros Moreno Herrera (Intl Vendor) [mailto:v-mim...@microsoft.com]
Sent: 15 February 2011 10:18
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] wix us
INSTALLLOCATION is automatically a public property you can set from a command
line or with a custom action or from the UI etc.
In fact all directories are msi properties that can be changed, they need to
be public (ALL IN CAPS) if you want to change them from the command line
though. (see Rob's li
Hi,
To set a property from the command line you simply just set the property to
be equal to the required value.
e.g.
Msiexec /i installer.msi FULLYQUALIFIEDCOMPUTERNAME=Kevinspc.buyseasons.com
SERVICEUSER=bob etc.
Remember to make all your properties public my making them all CAPS to and
you may
Use the heat option -var to point your file@source to a preprocessor variable
that you can then set in your wixproj or candle command line.
E.g.
heat.exe dir ..\_Release\Application -srd -sfrag -gg -dr AppFolder
-template:fragment -cg Application -sreg -pog:Binaries -pog:Symbols
-pog:Satellites
I'm not sure what you are trying to achieve, the windows installer service
already logs during these events and you can write to the log from custom
actions...
All you need to do is pass the /l parameter...
See also
http://support.microsoft.com/kb/223300
-Original Message-
From: Hareend
I don't think the version key that you are using is very reliable, I don't
have it on my machine but I do have the InstallPath.
Msdn states that the reglocator key column is of the type regPath which is
formatted so properties should be usable, but I don't think you can guarantee
the search order
If you have a directory element with no @Name it just makes the @Id an alias
of the containing element.
So your code makes any files targeted to MyApp.Binaries go in the same
location as INSTALLDIR.
-Original Message-
From: MeCoco [mailto:vcotirl...@hotmail.com]
Sent: 09 March 2011 15:03
Put a launch condition in that cancels your installation if msmq is not
installed.
If you really need to install msmq for your user use a bootstrapper that
installs it before your msi is called.
-Original Message-
From: Matthew Slane [mailto:matthew.sl...@thetrainline.com]
Sent: 09 March
I can't see your code properly but it will probably be because your MSI is 32
bit and running on a 64 bit OS. Windows automatically transforms the folder
to the x86 one.
If you want to target program files on a 64 bit OS you should create a 64 bit
MSI.
Dave
-Original Message-
From: wsjou
You will get the ice 69 error because windows installer can't know for sure
if that feature is being installed. If you can guarantee in all situations
that the main feature will be installed when you install the optional
feature, you can ignore (suppress) the error.
What should also work is that
MajorUpgrade was indeed introduced in wix 3.5.
I would try re-installing it and see if that helps, make sure you get the
release version of 3.5.2519 or try a weekly build of 3.6.
(http://wix.sourceforge.net/releases/)
Once that is done open your solution in visual studio and it should run the
up
Won't the windows installer have a file lock on the log file until the
installation is complete?
So you are looking at doing it in a bootstrapper of some sort or maybe just
specify where you want the log file in the first place with /l.
Dave
-Original Message-
From: Thai-Hoa Nguyen [mail
The windows installer is finding the path from the registry correctly as
C:\Program Files\Java\jre6, but your MSI is 32 bit so if you try to use it,
it will automatically be converted to the 32 bit location.
Best practice is to use a 64 bit msi to install 64bit or anycpu software onto
64 bit opera
:timoth...@gmail.com]
Sent: 21 March 2011 13:55
To: General discussion for Windows Installer XML toolset.
Cc: David Watson
Subject: Re: [WiX-users] 64-bit java registry detection?
Is there any way to disable path translation itself? Our code && installer
are 32-bit which we would like
I believe Dblock's extension does oracle via odbc.
http://msiext.codeplex.com/
-Original Message-
From: Dick Van den Brink [mailto:d_vandenbr...@live.com]
Sent: 21 March 2011 14:52
To: bharat.ja...@gmail.com; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating new Oracle
Do you have a ServiceControl element that stops the service on install?
-Original Message-
From: Matthew Dodkins [mailto:matthew.dodk...@gmail.com]
Sent: 24 March 2011 10:33
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Error 1923 upgrading a service
Hi there
I'm having p
ooks like this :-
>
> Stop="Both" Remove="Uninstall" Wait="Yes" />
>
> Thanks
>
>
> On Thu, Mar 24, 2011 at 3:54 PM, David Watson wrote:
>
> > Do you have a ServiceControl element that stops the service on
> install?
> >
>
Hi,
I am playing with burn again and I am trying to make a windows installer 3.1
package.
I am using a util:FileSearch on the msi.dll to see what version is installed
but I am struggling to work out what to put in my @DetectCondition.
If I try DetectCondition="MSIVersion > 3.1" Burn fails as the
ComputerName should work on msi verions 4 and up.
http://msdn.microsoft.com/en-us/library/aa368009(VS.85).aspx
I use [LocalMachine] when creating local accounts...
-Original Message-
From: kim [mailto:contactme...@gmail.com]
Sent: 24 March 2011 18:34
To: wix-users@lists.sourceforge.net
on.
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Thursday, March 24, 2011 11:45 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Get computer name??
ComputerName should work on msi verions 4 and up.
http://msdn.microsoft.com/en-us/library/aa368009(
ou tried it in the same format as
Package/@InstallerVersion:
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm
So for 3.1, use 301. Etc...
Don't know about your second question.
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: 24 March 2011 18:06
To: Ge
I now also have a wixlib with the windows installer 3.1 package in it too.
Marvellous!
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: 25 March 2011 12:22
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] version comparisons in burn
I think your tachyon relay got set to 2011 accidentally, you may want to aim
it at a time range to get answers appropriate to Wix 7.5.
Before you do though some 2011 lottery numbers would be good.
But seriously I'm not sure what you are asking, if you choose Install from
the build menu the msi wil
What is special about your registration that means you can't just heat them,
your code implies it's just regasm?
-Original Message-
From: Asker Brodersen [mailto:asker.broder...@esri.se]
Sent: 06 April 2011 06:41
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Too many CA:s (LG
If you are following the major upgrade rules
(http://wix.sourceforge.net/manual-wix3/major_upgrade.htm) your 1.1.0.0 dll
should be upgraded to 1.1.0.1. You should note that the component code of
this dll should not have changed. If it's not create a log and see what's
happening.
As to your need t
I want to
accomplish, and it works as long as I don't have too many dlls to fill up the
available sequence numbers after MsiUnpublishAssemblies. But I do...
/Asker
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: den 6 april 2011 11:30
To: WiX-users@lists.sourcefo
Hi,
The best way of doing this is exactly what you think is a bad idea. Store
this dll in a well know location or source control and refer to it as part of
your build process.
The Gac is actually a more complex structure than it appears in the
simplified windows explorer view. You can investigate
1, I think you may be missing Uninstall from your key path.
e.g.
"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\[ProductCode]"
2, Not sure what you are aiming at here, dtf is an api that helps you access
the windows installer, did you make a custom action project?
3, I've not really done i
bootstrapper could actually be a custom action, I don't
know if that would work or not.
On Fri, Apr 8, 2011 at 4:40 AM, David Watson wrote:
> 1, I think you may be missing Uninstall from your key path.
> e.g.
>
> "SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\[Product
http://wix.sourceforge.net/releases/3.5.2519.0/history.txt
the Final 3.5 release has all the history.
-Original Message-
From: Inulitka [mailto:isoum...@opentext.com]
Sent: 12 April 2011 14:50
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] What's new in WiX 3.5
thanks, but
Hi,
Have you tried putting elements under your for the
extra files?
Dave
-Original Message-
From: John Robbins [mailto:j...@wintellect.com]
Sent: 14 April 2011 07:00
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiX 3.6 Burn Problem -- How to run EXE in
place instead of cac
You can version lie, buts its usually not a good idea as the file will get
replaced every time the installation is run (it's what installshield does
when you click "always overwrite").
If you really need to do it then you set File@DefaultVersion to a valid file
version.
Dave
-Original Messag
to change the file and still have it removed as
all the other files on uninstall.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-----
From: David Watson [mailto:dwat...@sdl.com]
Sent: Thursday, April 14, 2011
Its works for me without using the @IP attribute but I have also never used
@Secure, do you get anything useful from the log?
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: 18 April 2011 22:46
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] IIS: WebAd
Is your UpgradeCode the same as your previous MSIs?
Also are you updating the ProductVersion correctly each time ?
Schedule should have a default so you do not need to specify it.
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm
Dave
-Original Message-
From: Tyler Walters [mail
Did you create a full DTF custom action project or just add the
references/attribute to a normal c# one?
A DTF custom action dll has the c# dll embedded in it as a resource with a
manifest file...
Dave
-Original Message-
From: Dick Van den Brink [mailto:d_vandenbr...@live.com]
Sent: 20
Begin Check");
return ActionResult.Success;
}
}
}
Is there some security permission or something needed?
What is DTF an acronym of?
Regards,
J.
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: 20 April 2011 16:04
To: wix-users@lists.sourceforge.net
Subj
Hi,
I have been trying to roll a few msps together into an installation bundle
and I am getting some odd errors.
I am using wix 3.6.1615.
If I use the unmodified WixStandardBootstrapperApplication.RtfLicense and
build and click through to the install i get the following errors in the log
and my p
Why not just write the information you require in the registry and store it
in a public property in each MSI.
That way you can generate your product code as normal and run no risks of
current or future problems with not following the guidelines for GUID
generation.
You can even make it more human
You would also need a condition that accounts for the situation when someone
disables the loading of your addin from the manager as there would be no key
as it is removed and a key added under
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Add-in Manager
From: http://support.microsoft.com/
I always create a local account to run our websites under, that way I can be
very explicit in what permissions it has, which of course is not many.
I do have some similar code to work out the IIS_WPG/IIS_IUsers group name
though.
-Original Message-
From: Michael Osmond [mailto:mosm...@ba
The relevant parent of util:permissionex is createfolder.
Put a component in your directory tree that has a CreateFolder with a
permissionsEx nexted in it.
An example...
-Original Message-
From: CoolBreeze [mailto:c
can I avoid that, but still add the permission I
need to the folder?
On Tue, Jun 14, 2011 at 5:23 AM, David Watson wrote:
> The relevant parent of util:permissionex is createfolder.
>
> Put a component in your directory tree that has a CreateFolder with a
> permissionsEx nexted i
Crypto\RSA\MachineKeys
Thanks again for your help.
On Tue, Jun 14, 2011 at 7:43 AM, Da
="SourceDir" I get
an error stating that "AppDataFolder" is not a valid root directory.
On Tue, Jun 14, 2011 at 9:52 AM, David Watson wrote:
> If you reference anything in a fragment then the entire fragment will be
> included in your installer.
>
> So if
;
>
> This doesn't seem to be working, because when I navigate to the above path
> and continue to Microsoft\Crypto\RSA\MachineKeys, "Network Service" has not
> been added to the MachineKeys folder along with the permissions I
> specified.
>
> On Tue,
DataFolder" should provide the complete path to the
> > "Application Data" folder, which should be "C:\Documents and Settings\All
> > Users\Application Data" as this is being installed on a Windows 2003
> > server.
> >
> >
> >
eKeys.
I'm not trying to create a new folder just add the user to the existing
folder along with permissions.
On Wed, Jun 15, 2011 at 11:34 AM, David Watson wrote:
> The following works, I just tried it.
>
>
>
>
>
>
NOT
Installed
ASPNETREGIIS AND NOT Installed
ASPNETREGIIS AND NOT Installed
ASPNETREGIIS AND NOT Installed
On Wed, Jun 15, 2011 at 12:20 PM, David Watson wrote:
> You must be doing something to break it then. You could post your code
I think that the only privilege that you can set in Wix is 'Logonasaservice',
via the user element.
I had to do this by custom action years ago from installshield.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 22 June 2011 10:32
To: General discussion fo
I simply use this...
.Net Framework 4.0
-Original Message-
From: Sidky Macatangay [mailto:y2k...@gmail.com]
Sent: 22 June 2011 06:21
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bootstrapping .NET Framework 4.0
I have both .NET Framework 4.0 and Windows Install
Yes you are probably correct depending on exactly how you are supporting
multiple brands.
If you want 2 identical products but the installation branded with different
logos and installed to a different location, your best bet is to make
multiple msis (you can do this from a shared codebase to simp
The MSI file replacement process says that if a non-versioned file has been
modified since installation (even if it was the installer that modified it)
then it will not be overwritten on upgrade. See
http://msdn.microsoft.com/en-us/library/aa370532(VS.85).aspx
Did you try that before writing your
32 bit (x86) installers can indeed write to wow6432nodes and do so by by
default.
Specify the key you wish to write to and omit Wow6432Node as they will be
redirected there automatically.
http://wix.sourceforge.net/manual-wix3/write_a_registry_entry.htm
Its also worth noting that Microsoft say it
One day someone should implement a @Persist on the property element, it could
even have ="yes" or ="encrypted".
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 08 July 2011 09:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-u
You can embed a custom manifest to a pre-built executable using the MT.exe
tool.
http://msdn.microsoft.com/en-us/library/aa375649(VS.85).aspx
mt.exe" -manifest "setup.exe.manifest" -outputresource:"setup.exe"
-Original Message-
From: Kryschan [mailto:christian.hennig@wincor-nixdorf.c
Are you passing "C:\Windows\system32\calc.exe" and not
"C:\\Windows\\system32\\calc.exe".
Just a guess.
-Original Message-
From: Anand, Animesh [mailto:animesh.an...@igatepatni.com]
Sent: 25 July 2011 09:44
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
-bf binds the files into the wixlib making a 'super' merge module that can
indeed be taken away and reused without any binaries. We use this
functionality many times every day. A wixlib is a wixobj file glued to a cab
file with the binaries in it.
What errors are you getting when you try to do thi
Without seeing your code/project I can't be specific but I can explain what
we do briefly.
We build with votive in VS 2010.
A wixlib project has a fragment with component groups in it. The components
in the groups are under directoryRefs. Bindfiles is checked.
The consuming MSI projects have a d
1 - 100 of 358 matches
Mail list logo
