You'd have to extract the Binary out with the CustomAction.
Michael wrote:
Hi,
I'm new to Wix. I'm using Wix v2. I have dll CA. I need to pass a exe
as dll CA data which is referred in binary.
sample code snippet,
CustomAction Id=ImportFile Property=ExecCmdLine Value='[UTIL]
/import
Commit custom actions run at the very end, by design.
Michael wrote:
Hi,
I have set of CA(commit) to executes on uninstall. I'm running CA after
'MsiUnpublishAssemblies'. While executing CA, I'm getting error in CA
dll that file not found. I want to execute CA before all files are removed.
And Class and ProgId elements.
Karl Denning wrote:
Hi
Don't use self-registering because it is not transactional.
Instead, use the TypeLib and Interface tables
karl
Dear Sandun,
I think that you can write File Name=MyComObject.dll
SelfRegCost=1 ... for the DLL in question.
Actually, WiX supports this already without having to execute code. Under
your PatchBaseline element add the Validation element and set
ProductCode=no. The double-click scenario for the resulting MSP will
only apply to the default instance (the instance you created the patch from)
but it will
If you explicitly set REINSTALL then all other feature properties like
ADDLOCAL are ignored (because REINSTALL takes precedence; see
http://msdn.microsoft.com/en-us/library/aa371175.aspx).
The default REINSTALLMODE is also omus, so unless it is explicitly set or
defined in the Property table
What version of WiX v3 are you using. A while back I made a change to
support the actual database schema so if your MSIs don't match the schema
WiX expects it shouldn't be a problem. Now, if your target and upgrade
database schemas different the error is there because Windows Installer will
fail
Are you still having the same problem with recent builds? A month or two ago
changes were made to fix a couple of issues with delta patching.
On Tue, Aug 19, 2008 at 5:57 AM, Tony Juricic tjuri...@tradestation.comwrote:
Ok, that makes sense. However, I can't get it to work either way. The
In a verbose log Windows Installer 3.1+ will add a line line SELMGR: A
component *foo* is registered to feature *bar*, but was removed from the
feature., followed immediately by something like SELMGR: Removal of
components from a feature is not supported. But this will not fail the
patch. Instead
So I guess the answer is that I have to write a custom action!?
Chris
Does it still do this if the wait value is zero? (or no). It won't start it,
but I'm wondering if it will still be catastrophic.
Phil Wilson
-Original Message-
From: Chad Petersen
Hello,
can i check for an installed IIS and list the available application pools?
The avaliable application pools should be listed in a listbox control.
Thanks
Thomas Bahn
--
I will be out of the office starting 04/03/2009 and will not return until
04/26/2009.
I will respond to your message when I return.
If anything urgent, please contact Brad Smith
--
I assume you mean a minor upgrade MSI, since for a patch this shouldn't be a
problem unless you're using a minor upgrade MSP with bad validation bits
targeting newer ProductVersions).
A minor upgrade MSI won't apply by default. It has to be reinstalled -
explicitly setting the REINSTALL property
That did the trick - I had a feeling it would turn out to be something pretty
simple..!
Thanks Neil
Have you include PropertyRef Id=NETFRAMEWORK20INSTALLROOTDIR / in
you code?
Neil
-Original Message-
From: Paul Nearney [mailto:paul_near...@hotmail.com]
Sent: 02 April 2009 17:07
Hi All,
i am stumbling around with my first Wix Project using variables.
Could someone explain when i had to use $(var.xyz) and !(loc.abc)?
Why i couldn't write things like that in my Directory Attribute?
Directory Id=unique
ende?lp=endep=thMx..search=unique_id$(var.abc) Name=$(var.abc)
Error:
Hi,
I set few environment variables from my wix installer, and refer them from a
console application (C#), whcih gets launched at the end of my WiX
installer. (I have a custom action to launch that console app, when the user
presses the 'Finish' button of the msi)
But my console application
This will completely break silent / unatended installations. You should
prompt the user in your installer UI using public properties (they can pass
to the installer whether running silent, basic, or reduced UI (required
then) or in full UI (just defaults then). WiX does have custom actions for
Hello,
I tried to redo what I did in my first attempt and now get the following
warnings (although I think my first attempt resulted in some error):
C:\Code\SVN\Deployment\CoreRelease.wxs(106): warning LGHT1076: ICE30: The
target file 'snyxsaz9.dll|PropertyDB-DL
might be installed in
The following code causes
MyApp.wxs(MyLineNo) : error LGHT0130 : The primary key
'regCEECC3C927D10BCB192BEE13F4F46715' is duplicated in table 'Registry'.
Please remove one of the entries or rename a part of the primary key to avoid
the collision.
Directory Id=ProgramFilesFolder
I was on vacation during that time in February, so I missed this thread until
Jesper brought it to my attention privately.
I think this problem was a bug in DTF, #2710297 on SourceForge. The bug was
that DTF CAs could fail to launch when a previous CA changed the working
directory (because MSI
Thanks for responses.
1. setting the SKIPCONFIGUREIIS property via an immediate CA (scheduled prior
to ConfigureIIs of course) to simply skip IIS configuration when the target
host already has the website installed would require us having some way to
determine if the target host already
Hi, Im trying to change the default blue color of groupbox text, but no
success.
Tried to apply other font with other colors but still default blue
String Id=abc{\WixUI_Font_Normal}Modelos e Recomendações/String
Control Id=Gbox1 Text=!(loc.abc) Type=GroupBox X=17 Y=45
Width=250
The documentation for the WriteEnvironmentStrings action @
http://msdn2.microsoft.com/library/aa372883.aspx state that the variables
are not effective in the current installation. So when you launch your
console app from the installer process the environment variables are
inherited from the
As long as your shared resources are in a component with the same GUID
(i.e., your instance transforms do not re-GUID your components) yes, Windows
Installer (and fusion for GAC assemblies) do keep a reference count. Bear in
mind, however, that if you uninstall a patch for any instance files are
Conditions are only evaluated at initial install unless they are transitive.
To better diagnose the issue, do you have verbose install logs from
installing QFE2 and SP1?
On Fri, Jan 2, 2009 at 10:34 AM, Ryan Parlee list...@jesca.com wrote:
I am trying to understand why some things are not
Along those same lines, you should consider never using the ProductVersion
property in your installation for things like directories or registry keys
(if you change them in a major upgrade, you break component rules). That
said, you might consider not showing the ProductVersion property for the
Tried using underscores and renaming; still get the same error (CNDL0150:
Undefined preprocessor variable).
-Original Message-
From: Jason Ginchereau [mailto:jason...@microsoft.com]
Sent: Thursday, April 02, 2009 5:55 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using
I use spaces in my project names and project references, and they're all
fine.
I suspect his problem is something else. I'm not sure what that is, since
this exact scenario, even down to the environment seems to match.
Chris
On Fri, Apr 3, 2009 at 12:29 PM, Eric Brown (REDMOND)
Also, there is that yellow warning icon on the project reference. I don't know
what that means, and I can't find a reference in the documentation.
-Original Message-
From: Christopher Karper [mailto:christopher.kar...@gmail.com]
Sent: Friday, April 03, 2009 10:17 AM
To: General
On Fri, Apr 3, 2009 at 8:24 PM, Eric Brown (REDMOND)
eric.br...@microsoft.com wrote:
Also, there is that yellow warning icon on the project reference. I don't
know what that means, and I can't find a reference in the documentation.
Normally that means that Visual Studio has failed to resolve
That is VS saying the reference is invalid somehow. I'm not sure what the
specific problem is, but have you tried deleting the reference and
recreating it? Sorry I can't do more to help right now, but I'm wrestling
TFS and Team Build, and it's winning.
Chris
On Fri, Apr 3, 2009 at 1:24 PM,
I have this wxs file to install binarys and a website in IIS. The
installation works fine. But just during uninstall, only the binary folders
are removed. The IIS website remains there (though the status becomes
unknown). I tried the verbose log, but didn't see any error/warning there.
Can
Multiple times. It always comes back yellow. There's no tooltip to provide
any further feedback. (Also, I've tried this with a separate dummy project -
I get the same problem.)
-Original Message-
From: Christopher Karper [mailto:christopher.kar...@gmail.com]
Sent: Friday, April
how does the ProjectReference tag look in your .wixproj file?
On Fri, Apr 3, 2009 at 9:13 PM, Eric Brown (REDMOND)
eric.br...@microsoft.com wrote:
Multiple times. It always comes back yellow. There's no tooltip to provide
any further feedback. (Also, I've tried this with a separate dummy
Learning WiX, getting into patching and have all sorts of confusion. But,
maybe someone can clarify for me:
When running torch on two .msi files (the original and the updated one),
torch isn't going to find differences in referenced merge modules is it?
Which means my transform file isn't going
ProjectReference Include=..\simple\simple.vcproj
Namesimple/Name
Project{51fd4fe2-5128-4557-b23c-be67ca3fe745}/Project
PrivateTrue/Private
/ProjectReference
-Original Message-
From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com]
Sent: Friday, April 03, 2009
I seem to remember that VC++ projects are not supported as project
references as they do not use msbuild. Please correct me if I'm wrong
though..
/Simon
On Fri, Apr 3, 2009 at 9:31 PM, Eric Brown (REDMOND)
eric.br...@microsoft.com wrote:
ProjectReference Include=..\simple\simple.vcproj
Yeah, I believe that would be the problem. That's the missing piece of the
puzzle.
Chris
On Fri, Apr 3, 2009 at 2:40 PM, Simon Dahlbacka
simon.dahlba...@gmail.comwrote:
I seem to remember that VC++ projects are not supported as project
references as they do not use msbuild. Please correct
That does seem to be the problem; if I use a sample C# project, it works fine.
It would be nice if this was more obvious. Sigh.
-Original Message-
From: Christopher Karper [mailto:christopher.kar...@gmail.com]
Sent: Friday, April 03, 2009 11:56 AM
To: General discussion for Windows
MSMs would already be merged into the the MSI at that point, so any
differences in your MSMs will be visible. But it depends on your patch
authoring. What does your patch source file look like? Can you post it or a
sample online?
On Fri, Apr 3, 2009 at 11:24 AM, Stryder Crown stryde...@gmail.com
In your verbose log, what does Windows Installer think is the Action state
for this component on uninstall? You're looking for a line that says something
like this:
MSI (s) (4C:88) [14:30:42:128]: Component: Site; Installed: Local;
Request: Absent; Action: Absent
It should say
Good to know, thanks!
-Original Message-
From: Heath Stewart [mailto:clubs...@gmail.com]
Sent: Friday, April 03, 2009 3:16 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Does Pyro (or Torch) ignore 4-th version number?
In a verbose log Windows
Setting the SKIPCONFIGUREIIS property via an immediate CA (scheduled prior to
ConfigureIIs of course) to simply skip IIS configuration when the target host
already has the website installed would require us having some way to determine
if the target host already has the website installed
42 matches
Mail list logo
