Ideally, configuration files shouldn't be installed. Install a default and
copy it to a user-writeable directory or just generate a default config in a
writable location on first run. If you're unable to fix the code for some
reason, you can change the file's permissions at install time using
util:
There's such a thing as a .zap file for installing exes with GPO but it is
limited in what it can do. Mass deployment systems other than GPO handle exes
much better.
Windows Installer 4.5 added multi package transactions but I seem to recall
Rob saying it wasn't entirely reliable in some situation
You can't do it. I use a separate msbuild step to call Saxon to transform my
XML. XSLT 2 is much nicer anyway.
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent: 26 February 2013 19:17
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat.exe XSLT parame
Use the Wix project properties to set the pre-processor variable to an
msbuild property e.g. SprintBuild=$(IsSprintBuild). You can initialise the
msbuild property via the build definition, an .rsp file, in tfsbuild.proj or
however you like.
-Original Message-
From: Robin66 [mailto:aliesch.
I use Nabble to search the archive.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-users-f6875
60.html
You need to include COM registration information when you install COM DLLs.
Look up "heat" in the wix help. That's a tool that gathers COM registration
from the DLL which you ca
I'm not sure that I follow the question, but all the options to heat can
viewed with "heat /?". If you can't achieve what you want with heat then
you'd have to wrap it in an MSBuild project or edit the wixproj.
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent:
The only thing I can think of right now is that WcaFinalize has been called
prematurely ?
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 25 February 2013 14:41
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WcaGetProperty returning Invalid hand
See the Wix help for CopyFile.
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent: 21 February 2013 16:22
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Rename File based on ArgumentpassedtoMSIInstallation
Thanks Peter..
Another question is
does
Yes, I'm talking about the file & component of the file that you want to
copy/rename.
FFF should be replaced with the Id of the File element.
CCC should be replaced with the Id of the Component that is the parent of the
same file element.
CostFinalize is just the place in the execute sequence wher
You can use the ProductCode property within the MSI.
http://msdn.microsoft.com/en-gb/library/windows/desktop/aa370854%28v=vs.85%29
.aspx
If by "package" you mean a bootstrapper or something else external to the MSI
then you can open the MSI with InstEd or Orca and examine the Property table
for t
You might be missing the necessary root certificate on those machines. I
think this is the link you need. Some certificates are updated by Windows
Update but not all so look at the certificate chain of the exe (right click /
properties) on an affected machine to see if it is installed.
http://www.m
http://www.lines-davies.net/blog/?p=12
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent: 20 February 2013 18:01
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Elminate %%filenametype%% during Heat.exe
Hi peter thanks for the reply.
Can you poin
Not really. I use XSLT.
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent: 20 February 2013 16:55
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Elminate %%filenametype%% during Heat.exe
Hi all,
I just want to eliminate some of the files during Harve
I think you have done the right things.
It's better (i.e. more reliable and easier to change) if you use a
SetProperty element to set the source property to the actual installed
location of the source file. This avoids hardcoding the source file path.
Likewise use SetDirectory to set the source &
Bundle/@IconSourcefile
-Original Message-
From: Persson, Lars [mailto:lars.pers...@diadrom.se]
Sent: 20 February 2013 10:28
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Icon for bootstrapper in add/remove
Hello
I want to add an icon for the application in add/remove. There is
It looks OK. Make sure the file
E:\Websites\SCBUDirect\Website\SCBUDirect.B2CWeb\App_Config\basic.log4net.dev
exists on the machine that you install on.
The next step would be to generate and examine a verbose log.
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Se
You could use the CopyFile element to create a file at run-time.
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent: 18 February 2013 21:18
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Rename File based on Argument passed to MSI Installation
Hi,
I
as a customer support issue instead of guarding
against it in your installer?
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Thursday, February 14, 2013 6:57 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Solved! RE: RegistryS
d files" are but I
will look that part up to see how I can use these.
As for the tutorial, it does not talk about lib files only fragments.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: February-15-2013 11:22 AM
To: General discussion for Windows I
There might be a wixlib example in the wix tutorial but I can't access it at
the moment.
A wixlib is like a compiled wxs file containing 1+ fragments. Instead of a
wixobj it's compiled into a wixlib. Optionally it can have the files
referenced added to the wixlib file in a cab (a bound wixlib) whi
Create a directory with the ID set to the same as the MSIProperty name, i.e.
INSTALLLOCATION. When the bootstrapper passes the property to the MSI, it
overrides the directory's default path in the MSI
-Original Message-
From: Sam Boman [mailto:s...@samb.se
Yep, the Canon installers are the scourge of the deployment world ;) Us too.
Sorry I didn't see your message in time.
http://kb.sdl.com/#tab:homeTab:crumb:7:artId:4654
-Original Message-
From: Arnette, Bill [mailto:bi...@signalscape.com]
Sent: 13 February 2013 18:59
To: General discussion
That, or add the generated wxs file to your project in visual studio.
-Original Message-
From: Yawar Khan [mailto:yawar.k...@live.com]
Sent: 13 February 2013 07:14
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat.exe
SET WIX=""
SET WORKING=""
*To harvest*
"%WIX%/bin/hea
Your last approach is correct. In general, you:
Place resources in a fragment in a separate file.
Add the file to the project.
Reference resources from your main wxs file (or any wxs file that it already
references) using an xxxRef.
When candle runs, it compiles the wxs file into a wixobj because
Regular expressions are useful here if you know them:
http://www.w3.org/TR/xpath-functions/#string.match
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: 11 February 2013 19:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-user
I'm not aware of any tutorials but if you search this list, a few people
including myself have posted xslt code before.
For a one-off like that, I'd just use my text editor's search and replace
function.
-Original Message-
From: Gabriel Ivanes [mailto:g...@fastmail.net]
Sent: 11 February
The default Id thing was a recent addition. Wix 3.6 maybe.
Your light error sounds like a possible Wix bug. Its cropped up on the list
before but that person turned off validation to work around it.
You could validate interactively with orca or instEd which aren't based on
the Wix code. That's wha
Yes that's OK for the reason that you suggest. In fact, if you omit the IDs
from file and component, wix will generate them and are the file name with
any invalid characters substituted.
-Original Message-
From: Sam Boman [mailto:s...@samb.se]
Sent: 11 February 2013 15:23
To: wix-users@li
One component per file works well in most cases. The link below suggests help
files go in their own component.
http://msdn.microsoft.com/en-gb/library/windows/desktop/aa368269%28v=vs.85%29
.aspx
Non-versioned files have their own update rules, but basically it works
without you having to do anyt
See the "Heat" tool in the Wix help file.
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent: 08 February 2013 16:17
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Create MSI package for Website
Hi I am new to Wix,
I have created a MSI package having
You can't use properties as directory names because the type of the Name
attribute is LongFileNameType, not Formatted (see the Wix help), and property
names are not substituted except in formatted types. Even if you could do it,
it would be a bad idea because it would break the auto component guid
If you need directories that you can set yourself, use a structure like this:
If no properties are passed on the command line, the structure above is used:
the website goes into [ProgramFiles]Chaitanya\website and the otherfiles go
into in
Have you seen this page ?
http://msdn.microsoft.com/en-gb/library/windows/desktop/aa371614%28v=vs.85%29
.aspx
Scroll down to "INSTALLMESSAGE_FILESINUSE"
The "files in use" error message is in the MSI's Error table (error 1603) and
could be changed with a wix element.
I'm not sure how the 2 tie t
The problem is that the MSI package is not in the temp location at build
time. It's a bit of a weird scenario. What happens if you place the extracted
msi(s) in the build machine's temp directory ? Obviously that wont work if
the bootstrapper remembers the resolved path.
You might end up having to
You could host the MSI on your own web server, if you have the facilities.
-Original Message-
From: Yawar Khan [mailto:yawar.k...@live.com]
Sent: 04 February 2013 12:20
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Office XP Primary Interop Assemblies (PIAs)
asprereq.
The
Extract the MSIs you need and include those in your bootstrapper at build
time instead of using the exe. It'll work much better too.
-Original Message-
From: Yawar Khan [mailto:yawar.k...@live.com]
Sent: 04 February 2013 11:39
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Offic
Wix has built-in support for detecting Dot Net. See "How To: Check for .NET
Framework Versions" in the Wix help.
-Original Message-
From: Yawar Khan [mailto:yawar.k...@live.com]
Sent: 01 February 2013 12:52
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Detect the existence of W
>From the wix manual: "GenericRead YesNoType specifying this will fail
to grant read access"
Im not sure if GenericAll overrides that or not.
Try adding:
Read="yes" ReadAttributes="yes" ReadExtendedAttributes="yes"
ReadPermission="yes"
-Original Message-
From: Kun Shi (ofox) [mai
The wixobj should be in the current directory unless you specify the -o or
-out switch
If you type candle /? It will describe the options.
-Original Message-
From: Kesavan, Lakshminarayanan IN BLR STS
[mailto:lakshminarayanan.kesa...@siemens.com]
Sent: 30 January 2013 13:36
To: wix-user
If you type "echo %wix%" (without the quotes) you will get the path of the
wix installation. Candle.exe is in the "bin" subdirectory of that location
-Original Message-
From: Kesavan, Lakshminarayanan IN BLR STS
[mailto:lakshminarayanan.kesa...@siemens.com]
Sent: 30 January 2013 13:06
To:
it's not liking. Not sure if the
command will do as expected but I will test it.
Kind Regards,
Natalie Carr
-----Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Wednesday, January 30, 2013 12:34 PM
To: General discussion for Windows Installer XML toolset
Keep deleting parts of the execommand string until it compiles. The " s
are most likely causes.
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 30 January 2013 12:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] IIS- delete hidden segment error
The application must supply these variables to
the servers when making any web service or restful call to the back end.
This is why generating the MSI is so necessary.
I hope this helps. Thanks for taking the time to reply.
- Greg
On Jan 29, 2013, at 7:25 AM, Peter Shirtcliffe wrote:
> If
If your MSI packages are always the same apart from that single configuration
file, one way to do it would be to exclude file from the MSI. Then create a
single, static MSI and let the application download the config file at
runtime and configure itself, if it hasn't already done so.
This would be
gards,
Natalie Carr
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Friday, January 25, 2013 10:53 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom actions failing on XP
Have you tried linking to the C++ runtimes statical
Have you tried linking to the C++ runtimes statically instead of to the DLLs
? The target runtime might be missing on XP.
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 25 January 2013 10:35
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom
Component conditions are evaluated in CostFinalize. Is your property being
set before CostFinalize ?
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 24 January 2013 07:30
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] conditi
Can you roll your 2008 VM back to a clean state before you installed either
the patch or the product and reproduce the error ? We're far from certain but
it could be a corrupted patch cache or something on the machine that has
touched the files somehow after caching.
Have you also tried creating
The wix help describes how to customize the standard dialog sets. See the
bottom of this page
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
Neil's blog also has an example
http://neilsleightholm.blogspot.co.uk/2008/08/customised-uis-for-wix.html
-Original Message-
From:
------
From: "Peter Shirtcliffe"
Sent: 18 January 2013 13:56
Your feature and condition both have level 1 which won't work - the
condition causes nothing to change.
The default value of INSTALLLEVEL is 1. This means any feature set to level
1
will be installed. To prevent i
If the installer installs the files, it'll remove them.
The best practice is not to install editable files - it leads to all manner
of trouble. Generate them (or duplicate them from installed, read-only
copies) from the application whenever they are missing, if that is possible.
-Original Mes
Your feature and condition both have level 1 which won't work - the
condition causes nothing to change.
The default value of INSTALLLEVEL is 1. This means any feature set to level 1
will be installed. To prevent installation, the feature level must be higher.
Keep the feature level as 1.
Set the c
Possibly the detectcondition is preventing removal. Check the value of KeyA
in the log during a removal.
-Original Message-
From: abs [mailto:mail.jie.ji...@gmail.com]
Sent: 18 January 2013 09:34
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] ExePackage uninstall doesn't work
H
In the last few wix versions, no guid is the same as *. To get no guid at all
you have to explicitly use Guid="".
-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: 17 January 2013 19:21
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-us
Use ISSQLSERVERSERVICEINSTALLED as the directory ID rather than the name. Set
the Name as the default directory name
It's the same way as you'd use INSTALLDIR (if you're familiar with the
convention) but setting the value from a registry search instead of on the
command line.
If it doesn't work, ch
ror 1923. Service
'ServiceName' (ServiceName) could not be installed. Verify that you have
sufficient privileges to install system services.
Thanks for the help :)
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 16 January 2013 01:38 PM
To: General disc
alled. Verify that you have
sufficient privileges to install system services.
Thanks for the help :)
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 16 January 2013 01:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
added a custom installer class to test if the service will install
using InstallUtil, I't doesn't do anything special like custom actions.
-Original Message-----
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 16 January 2013 01:26 PM
To: General discussion for Windows Ins
lling service using domain account
Hi Peter, the service installs perfectly using InstallUtil, an sc.exe, I have
no Idea why it's doing what it is.
-Original Message-----
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 16 January 2013 01:13 PM
To: General discussion for Windows
It's usually a missing dependency dll. A useful troubleshooting step can be
to take the set of files and use sc.exe and the services control panel to try
and install and configure the service manually on the same machine.
-Original Message-
From: Christoffel le Roux [mailto:christoffe...@t
Our pre-Burn chainer uses
Office 2003: Chainer.ProductInfo.IsComponentInstalled(new
Guid("{3EC1EAE0-A256-411D-B00B-016CA8376078}"))
Office 2007: Chainer.ProductInfo.IsComponentInstalled(new
Guid("{0638C49D-BB8B-4CD1-B191-050E8F325736}")
Those are the component codes of mso.dll
I don't have codes f
A util:ComponentSearch might be easier to work with. You could get the
component code from the interop MSI. All the MSIs that install that
particular dll ought to use the same component ID. Even developers should be
using the interop msi to install them the first place.
-Original Message-
I think you are getting attributes mixed up. The path goes in the FileSource
attribute.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 11 January 2013 14:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] assigning path for d
Any use ? community.flexerasoftware.com/archive/index.php?t-143660.html
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 09 January 2013 14:53
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Update progress bar from custom actions
Hi I am trying
I will just revert my changes back to the merge module format...
steve
-----Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: January-03-13 5:25 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLibs questions...
You have to dupl
You have to duplicate the code I'm afraid. The IDs must differ between the
two copies.
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 02 January 2013 18:49
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WixLibs questions...
I have about 10 WixLibs and th
Wix is open source. If you need a feature urgently, you're welcome to take
the source code and implement a solution yourself :) Otherwise it's a case of
hoping someone on the WiX team (or some other contributor) takes it on.
-Original Message-
From: Kannan24 [mailto:skan...@syncfusion.com]
Launch conditions always run, including during removal. Usually, you'd use
the condition: Installed or ... if you want to write a condition that's only
checked at first-time installation.
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 19 December 2012 15
VersionNT64 is undefined on a 32-bit OS so
Installed OR (SQLSYNCX64SEARCH > "0" AND VersionNT64)
would be
FALSE or (something AND FALSE) === FALSE
which would cause the message to display.
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 19 December 2012
Error 5 is access denied. Are you running the installation as administrator ?
-Original Message-
From: Marty Offe [mailto:marty.o...@harlandfs.com]
Sent: 17 December 2012 16:44
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How do to configure a Windows service to "Restart the
S
You could try setting Vital="no" on the File element. I'm not sure if that
applies to removal as well as installation.
-Original Message-
From: Nirmalraj Durai [mailto:nirmal.du...@gmail.com]
Sent: 17 December 2012 06:05
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Network pat
Permissions are not cascaded down to subkeys. There might even be a
bug/feature request still outstanding for it.
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: 06 December 2012 07:49
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Regisytry Entry Perm
n at least WinXP SP3 should be done in the
bootstrapper and removed from my MSI, right?
Should I move actions like closing running application from the MSI to the
bootstrapper too, and all things that could display any dialog/msgbox?
thanks for the answer
On 05/12/2012 18:02, Peter Shirtcliffe wrot
Yes, create the UI in a custom bootstrapper. The separation is: data
collection goes in the bootstrapper; modifying system state goes in the MSIs.
-Original Message-
From: up2date.cyb...@gmail.com [mailto:up2date.cyb...@gmail.com]
Sent: 05 December 2012 16:48
To: wix-users@lists.sourcefor
That sort of configuration is best moved out into the application or a
configuration utility so that you don’t have to reinstall should it ever need
to change. It would solve your problem.
-Original Message-
From: Grigory Konovalov [mailto:grigory.konova...@confirmit.com]
Sent: 05 Decembe
Try adding to the shortcut component, or put CreateFolder in
its own component and put it under the API_DirExample directory.
-Original Message-
From: Budde, Marco [mailto:bu...@telos.de]
Sent: 05 December 2012 10:21
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] ProgramMenuFol
I don't fully understand what you're describing but one difference from our
set-up is that we have the Wix projects each in their own solution. The MSIs
take a long time to build and most C# (C++, etc.) developers don't want to
build them when they press "build solution" during development, nor do
1. Making dual-purpose packages was difficult in MSI before version 5. At my
company, we still need to support Windows prior to Windows 7/Server 2008 so
MSI 5 isn't an option yet and we create per-machine installers. With MSI 5,
dual purpose packages are easier to create:
http://msdn.microsoft.com
iDatabaseOpenView(hInstall, "SELECT 'Data' FROM 'Binary' WHERE 'Name'
= 'Hasp'", phView);
MsiRecordReadStream(*phView, 1, szBuffer, &cbBuf);
CreateFile(szBuffer, GENERIC_WRITE,FILE_SHARE_WRITE, NULL, CREATE_ALWAYS,
FILE_ATTRIBUTE_NORMAL, NULL); }
Debugg
The argument to MsiDatabaseOpenView should be a handle to a database. That
would be there return value of MsiGetActiveDatabase. MsiGetActiveDatabase
takes and argument of an installation session which is what the custom action
is passed on entry. You've passed and uninitialized database handle to b
Search through the registry for a key with the same name that *does* have the
right permissions. There might be a 32/64-bit mismatch or registry
redirection or something like that.
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: 22 November 2012 09:19
To: 'Gener
I've had reproducible access denied errors in builds where the Windows
Indexing Service was locking files that I was writing. Excluding the location
from indexing fixed it.
-Original Message-
From: Parkes, Kevin [mailto:kevin.par...@wacom.eu]
Sent: 20 November 2012 11:55
To: wix-users@lis
ue Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
keith.doug...@statcan.gc.ca Telephone | Téléphone 613-951-4405 Facsimile |
Télécopieur 613-951-1966 Government of Canada | Gouvernement du Canada
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sen
>From the help for ElementPath
" Note that this is a formatted field and therefore, square brackets in the
XPath must be escaped. In addition, XPaths allow backslashes to be used to
escape characters, so if you intend to include literal backslashes, you must
escape them as well by doubling them in
Have your BA set a burn variable. Use this variable as the Value of an
MsiProperty element.
-Original Message-
From: victorwhiskey [mailto:victorhwhis...@yahoo.com]
Sent: 16 November 2012 14:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Is it possible to pass variables to t
ProgramFilesFolder is a Windows Installer property. It is evaluated at
runtime which requires square brackets around it and that will only work
where the type of the attribute it appears in is "formatted". The type of the
Value attribute of Property is just "string".
You'll need
Instead of Prope
INSTALLDIR must be persisted if you want to access it outside first-time
installation. This is usually done through ARPINSTALLLOCATION.
http://robmensching.com/blog/posts/2011/1/14/ARPINSTALLLOCATION-and-how-to-se
t-it-with-the-WiX-toolset
-Original Message-
From: Ingo Fischer [mailto:ingo
egistry key and insert it into the Directory declaration?
Regards
Anders
Peter Shirtcliffe wrote:
The default directory is whatever directory Id you set WIXUI_INSTALLDIR to,
so in this case it is INSTALLDIR, which is \ZZ_Installer.
If you change your directory structure to be
\\ and ensure the di
MsiGetProductInfoEx() can return the cached MSI location using an argument of
INSTALLPROPERTY_LOCALPACKAGE
We discussed doing something similar here once. I'm not convinced it's a
worthwhile exercise. You should rather test the functions of the software -
which you will be doing anyway. If a file
have
another file which needs to go into 'c:\program
files\\\Extensions\'.
Thanks.
Anders
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesday, 13 November 2012 9:29 PM
To: General discussion for Windows Installer XML toolset.
Subject:
result was very messy
when trying to uninstall. We would certainly like to prevent users from doing
this even if everybody agrees that it was done by accident and not
intentionally.
On Wed, Nov 14, 2012 at 4:52 PM, Peter Shirtcliffe
wrote:
> I think you can be in the non-elevated portion of
I think you can be in the non-elevated portion of the process multiple times
- the mutex only protects the execute sequence, where the system is being
modified.
-Original Message-
From: Hans ter Horst [mailto:hoshis...@gmail.com]
Sent: 14 November 2012 15:47
To: General discussion for Win
This is certainly possible.
1. The WixUI_InstallDir built-in dialog set will prompt the user for an
installation location.
http://wix.sourceforge.net/manual-wix3/WixUI_installdir.htm
You may even be able to detect the location of the existing tool, if you know
the MSI product codes of the version
hat for us and returns a
MSI property (which I use in the MSI)
Steve
-Original Message-----
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: October-31-12 12:29 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] custom actions in burn?
I imagine t
ook and 32 bit/64 bit checking for the bitness
isn't simple, we have a custom action dll that does that for us and returns a
MSI property (which I use in the MSI)
Steve
-Original Message-----
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: October-31-12 12:29 PM
To: General
I imagine that a Burn custom action would be part of the code of a custom
bootstrapper application that would set a variable during the appropriate
event. Could you not use a util:product search or utilL:registry search to
determine which outlook is installed ? Save you a lot of work unless you've
.'
Subject: Re: [WiX-users] Minor upgrade
Yeah...iam maintaing command line like.
msiexec -I $(.msi) REINSTALL=ALL REINSTALLMODE=vomus but it's not working.
Is it mandatory to maintain property tag like
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
S
: [WiX-users] FW: Windows 8
Are you sure, from what I have found the tile picture is a png not a icon.
Is there any way to change the tile size of the shortcut?
Thank you,
Michael Ogilvie
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesday, October 30
It's the shortcut icon. See the Shortcut element.
-Original Message-
From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com]
Sent: 30 October 2012 14:34
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] FW: Windows 8
Does anybody know how to change the pi
Is this a per-user or per-machine installer ? Are you loading the dll
dynamically ? Are you specifying the full path ? The current directory for a
custom action is, I think, System32.
Installing something to TEMP is a bit odd. TEMP is a per-user location and
will vary depending on installation cont
1 - 100 of 685 matches
Mail list logo
