On 04-Oct-11 02:00, Paul A. Steckler wrote:
> Does anyone know if macros like VS11_ROOT_FOLDER, etc., will be
> available in a coming version of the WiX toolset? Soon, maybe?
Historically, the detection properties were added during beta.
--
sig://boB
http://joyofsetup.com/
On 03-Oct-11 12:43, Brad Lemings wrote:
> So I located the .wxl sources with the appropriate text strings. I'm
> assuming I don't need the special markup in comments (e.g. _locIDText,
> _locComment)?
No, they're just comments for the localization team that contributed the
strings.
--
sig://b
On 04-Oct-11 15:06, Brian Lemke wrote:
> Because most of these are nested in folders created by the application. I
> would really like to use the RemoveFolderEX element found in Wix 3.6 but I am
> not allowed to use that version yet. I am forced to stay on 3.5
1. That's a false economy: The t
On 04-Oct-11 15:29, McCain, Jon wrote:
> If that is the case then you shouldn't need to worry about being a good
> install writer and just whack the folder or its subfolders that you don't
> control with your install.
Of course you should. If there's a failure or other rollback, the user's
data
Sure. In .NET you use try catch blocks rather then checking the exit code
of functions. In DTF, the View class (and others) will raise an
InstallerException which then exposes the GetErrorRecord() method which is
a wrapper for MsiGetLastErrorRecord().
Is there anything about that interop that lets you see the equivalent of
MsiViewGetError or MsiGetLastErrorRecord? There's typically more error info
available from those.
Phil Wilson
-Original Message-
From: Brian Lemke [mailto:brian.le...@apihealthcare.com]
Sent: Tuesday, October 04
Hi Peter...
It was a bit of a nuisance to get a verbose log out of the wmi install,
so I've been comparing the logs from the builds using the type 51 and type 35
work-arounds vs the builds just ignoring the error. The differences I see is
that TARGETDIR= in the early phases of all logs
Okay so the folders/files are then classified as customer data which is why
RemoveFile wouldn't work since you don't actually lay those files down. At
least that is how I am reading your response.
If that is the case then you shouldn't need to worry about being a good install
writer and just wh
Because most of these are nested in folders created by the application. I
would really like to use the RemoveFolderEX element found in Wix 3.6 but I am
not allowed to use that version yet. I am forced to stay on 3.5
-Original Message-
From: McCain, Jon [mailto:jon.mcc...@inin.com]
Se
Just curious here but why not use the RemoveFile element within the component
that initially installed the file or do you not own this file?
Also, AFAIK If you remove all files in the fashion above that directory will be
removed as well.
Jon W. McCain | Software Engineer - Install
phone & fax +
I'm hoping that someone can help me out. I cannot seem to figure out why my
custom action is constantly failing me. The action executes on uninstall and
is to browse the install folder and add files to the RemoveFile table (with a
few additional properties too) in the MSI so that the file is
VBScript is pretty straightforward.
Dim installer = CreateObject("WindowsInstaller.Installer")
And then
Installer.InstallProduct (path to msi, property list etc)
for each one.
I suspect PowerShell has similar capabilities.
Phil Wilson
-Original Message-
From: McCain, Jon [mailt
During an installation there may be more than those two. New ones may be fired
up to host custom actions. I agree, it all sounds normal to me.
Phil Wilson
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesday, October 04, 2011 1:53 AM
To: General disc
The subtle differences between the two are a bit beyond me since I've never
needed to distinguish between them. There's a list of considerations at
http://msdn.microsoft.com/en-us/library/aa367852%28v=VS.85%29.aspx which may
answer your questions. It's worth trawling through the MSDN.
For us, sett
Thanks, Peter... I can give it a shot.
I was a bit perplexed when I found that the Type 51 approach worked as I
expected when it installed remotely through WMI, as opposed to being run
locally on the computer. By and large our ops team uses a utility to manage
the farm and the installs are ru
I've just looked back at your original post which is how to avoid ICE48
errors. The ICE48 error is issued because ...
ICE48 checks for directories that are hard-coded to local paths in the
Property table.
(From
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368977%28v=vs.85%29
.aspx)
I
I was wondering maybe *before* CostFinalize? I'm just grasping around here...
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesday, October 04, 2011 10:24 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Dealing with
When calling another process from within a batch file that you want to waiting
merely add 'call' in front of it. I do this to utilize multiple batch files
with one call.
Jon
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Monday, October 03, 2011 6:52 PM
Nope... The actual path is just as vanilla as the example below. Straight
7-bit ascii...
Thanks
mark
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesday, October 04, 2011 10:24 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re
Could it be the file's encoding ? Declared as UTF-8 but written in something
else maybe ?
-Original Message-
From: Mark Modrall [mailto:mmodr...@mzinga.com]
Sent: 04 October 2011 15:17
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Dealing with ICE48 wa
Thanks for the response... I tried replacing my type 51 with
After CostFinalize, but now I get an error "The folder path '?' contains an
invalid character" when I run the installer locally.
Not sure where the ? is coming from...
Mark
-Original Message-
From: jhennessey [mai
For each file, you create multiple components but their Component/Source
attributes will point at the same file. The file will only be included in the
installer's cabinet once.
-Original Message-
From: Thomas Due [mailto:t...@scanvaegt.dk]
Sent: 04 October 2011 09:44
To: wix-users@lists.s
You can either use an xsl transformation on the generated wxs file that would
insert your progid (heat even has a switch to run one) or you could put the
progid and contents in its own component in a separate file and add that file
to the project.
The first has the advantage that you have a version
Hello,
I am wondering about file components and directories.
As I understand it, I have to point any component containing a file towards a
named directory.
But what if I need a file in several directories?
Currently I am thinking about making two separate installers with a common wix
library
That may be ordinary behaviour you are seeing. There are 2 msiexec processes
associated with an installation - the client-side exe and the server-side
service process. After the msiexec service has been used for something
(installation, repair, etc), it persists for a while (10 minutes maybe ?) in
25 matches
Mail list logo
