Thanks for the explanation.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com
From: Richard [mailto:legal...@xmission.com]
Sent: Thu 19/02/2009 23:52
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] DTF -
I think you missed the point. I can see there are two different entry points,
one for install the other for uninstall but what I can't see is the condition
that says to run one on install and the other on uninstall. (Using the SQL one
was probably a bad example as that has an override condition
I don't suppose you could point me in the direction of the code that controls
that for one for the WiX CA's so I can learn how to do it.
Thanks
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com
From: Bob Arnson
Hi,
I am calling my Custom actions After InstallFinalize Event.
Thing is that, I am doing various actions inside my Custom
action and it takes some time to execute all of them.
Rather than user waiting to see what is happening, I want to
send the
Something like this should do it:
UI
ProgressText Action=YourCAIdDoing something.../ProgressText
/UI
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com
From: Kusuma Sudheer Kumar (Tata Consultancy Services)
There is a helper function in wcautil that is usually a tell tale sign
you've found the code ::WcaGetComponentToDo(). The old school way (most
of serverca uses the old school) is to call
WcaIsInstalling()/WcaIsReInstalling()/WcaIsUninstalling() to determine
the scheduling.
Hi, this is a Visual Studio Add-in that you are referring to. You can create a
Visual Studio add-in by using the new project wizard, and
select the add-in project type beneath the Other Project Types - Extensibility.
There is some documentation at MSDN, but I have found the best guidance to be
I want my installer to be silent installation. for that I want to pass
the
values to all the properties.
I can want to give all the values in a text file and read them. But my
doubt
is when to shedule this custom action?
before executing the msi
msiexec /i /q aa.msi INSTALLDIR=
Do you want the text file to be read during ONLY silent installs or both
interactive and silent installs?
If both, schedule the CA somewhere before costing in both the UI and the
Execute sequence. Attribute it to run only once.
If only silent, schedule the CA somewhere before costing in only
Hi Bob:
It's not static data, it's dynamically picked up during install. If I
can create a table and add data to this table (in ca's), this would
suffice nicely.
Any help apreciated as to how to do this.
Cheers
Sean.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
You can also have an empty component group and add reference to it from the
product file. - this is what I do :^)
-Original Message-
From: Frederico Rico Apostolo [mailto:frederico.apost...@vantyx.com]
Sent: Friday, February 20, 2009 4:49 PM
To: General discussion for Windows Installer
Windows Installer does not commit files to the GAC until
InstallFinalize
(the end of the transaction). This prevents GAC assemblies from being
used or even referenced really during the installation transaction. I
think this design limitation is the root of your issue.
So, now I know the
Anyone have any thoughts on this? In my mind I am thinking that I would
need to transform
the Upgrade Code for each instance and the values in the upgrade table
to match for
windows installer to properly identify the specific instance I wanted to
upgrade such that
in my newer installer Instance1
Is there any way to extract the files to be installed from an MSI
package?
Thanks,
Jim
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open
I'm basically automating a currently manual process, and it's on our
list of things to do.
-Original Message-
From: Rob Mensching [mailto:r...@wixtoolset.org]
Sent: Thursday, February 19, 2009 8:42 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
I'd like to complain... I tried to find what condition should I use to find if
AJAX Extensions is installed, it's impossible because some1 u must say is very
active and that's good, great, have this signature full of products and
architectures, which makes hard to find information about that
You could try an administrative install:
msiexec /a xxx.msi
Jim Williams
-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com]
Sent: Friday, February 20, 2009 9:05 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Files
What happens when the data value you need contains what appears to be the
delimiter between independent properties within the CustomActionData class?
semi-colon...
-Original Message-
From: Rob Mensching [mailto:r...@wixtoolset.org]
Sent: Tuesday, February 17, 2009 10:52 PM
To:
In article e66649032ad92b42901bf5835c76a27f9...@harwood.x2systems.com,
Neil Sleightholm n...@x2systems.com writes:
I think you missed the point. I can see there are two different entry =
points, one for install the other for uninstall but what I can't see is =
the condition that says to
In article 499e7ecd.8000...@wixtoolset.org,
Rob Mensching r...@wixtoolset.org writes:
Using conditions to control your CustomAction install/uninstall
behaviors is primitive and usually insufficient... but the most
visible. Data driven CustomActions that modify machine state via
I leave the upgrade code the same for all instances. I have a dialog asking
the user whether they'd like to upgrade an existing instance, or install a new
instance (only if an existing instance is detected).
If the user selects to upgrade an existing instance, I store the product code
of that
I'm trying to implement a files in use dialog and I've noticed a discrepancy
between the values in Microsoft.Deployment.WindowsInstaller.MessageResult and
the values of the dialog box command ID's in WinUser.h. Here's what I see in
MessageResult:
public enum MessageResult
{
That's exactly it. This also happens to be the exact same way the
Windows Installer operates on all of its tables that install Resources.
That's why this model works well. IIRC, all of the WiX CustomActions
that install Resources work this way as well.
I learned this from the MSI SDK a long
Those Properties are essentially kill switches for the CustomActions.
I don't remember the scenarios off the top of my head but we added those
and the SKIPCONFIGUREIIS based on some needs. They are big red buttons
that completely kill the CustomActions. The Properties do not provide
fine
Option 1 may be the best. All of that install/upgrade/uninstall stuff
you listed on that line is good stuff and difficult to do well.
I think Option 2 won't work because your CustomAction will not be
elevated after InstallFinalize and thus will not be able to make the
COM+ configuration then.
You're right. Conditions are one thing that don't have a good way to
reference. Maybe put the Properties referenced by the Conditions in the
same Fragment, then use a PropertyRef?
Frederico Rico Apostolo wrote:
I'm using v3 votive in vs2005 and I lost sometime trying to have a fragment
Ick. smile/
Eitan Behar wrote:
You can also have an empty component group and add reference to it from the
product file. - this is what I do :^)
-Original Message-
From: Frederico Rico Apostolo [mailto:frederico.apost...@vantyx.com]
Sent: Friday, February 20, 2009 4:49 PM
To:
Actual I was thinking more along the lines of taking the files out of
one msi and putting them into my main package since I can't seem to call
an msi from inside my main one.
-Original Message-
From: Jim Williams [mailto:jimwilliam...@comcast.net]
Sent: Friday, February 20, 2009 12:50
John,
Thanks so much for this! :) That is much better news than what I was
hoping for. I am going to try it today.
A
-Original Message-
From: John Nannenga [mailto:john.nanne...@microsoft.com]
Sent: Friday, February 20, 2009 11:25 AM
To: General discussion for Windows Installer XML
That is what I did, and it was easy to do.
So what is the purpose of the DLLPathFromGAC attribute on the ComPlusAssembly
element? It doesn't seem like it has any use as of build 3.0.5006 unless you
are using to register a DLL that already was previously installed, and I'm not
sure what
Well, if both installers are written in WiX, just move the WiX File.../ source
into the main WiX installer. :-) However, if the one msi isn't written in WiX
you could do an administrative install, then create the WiX File.../ source
for the files using heat.exe, and add then add that WiX source
If memory serves me correctly (from last August), the issue here lies in the
MakeSfxCA processing. It only writes the Embedded UI entry points if there are
no CAs included in the project.
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
If you only need to do this manually one time, the Dark utility with the /x
option will decompile an MSI and extract all of the binary components,
including any embedded CAB files. You can then use a standard archive tool to
extract files from the CABs.
-Original Message-
From:
This is actually supposed to work. Though neither Fusion or COM+ where designed
with deployment in mind, so plenty of unexpected things seems to happen here.
This probably has something to do with Fusion, but I am at a loss to tell what.
Are you saying that you have had it working with a
I never had this functionality previously working. I am a new user to WiX (just
since the beginning of the month), going through the process of converting Wise
for Windows Installer projects (yes, it's an ancient tool!) to WiX.
Based on what Rob is saying, it does certainly seem to a Fusion
Note: Fredrik wrote the COM+ installation code. His answers are far more
authoritative than mine.
Don Benson wrote:
I never had this functionality previously working. I am a new user to WiX
(just since the beginning of the month), going through the process of
converting Wise for Windows
On top of that it was all written on Windows 2000 originally. It could have
something to do with the assembly name that is being extracted from the MSI
tables.
In any case I would also recommend going with your option 1 below, for the sake
of general robustness. As long as you can live with
It is interesting that you mention the Assembly Name from the MSI tables. When
I first got the error, I was looking in the ComPlusAssembly table and noticed
that the AssemblyName column was blank. I tried adding the AssemblyName
attribute for my COM+ assembly, thinking that it would help the
Yan,
Take a look at the mailing list posts from and related to Cody Cutrer's
enhancements to PermissionEx. I will also build a patch from my latest
efforts and attach it to issue tracker item 2612975.
Thanks,
Thomas S. Trias
Senior Developer
Artizan Internet Services
http://www.artizan.com/
I think I understand the component state approach but I am not sure this is
possible with the current implementation of custom tables as I can't see how
they can be associated with a component.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com
Volnei dos Santos wrote:
You are correct, Bob; I've right the wrong code here. But unfortunately it's
not the main problem. Man, I've tried millions of variants of this code,
including your suggestion. That's why I think the way I'm doing the thing
may be wrong...
Then start with a
Rob Mensching wrote:
WcaGetComponentToDo() is a nice wrapper that cleans up
much of the confusion.
You're welcome.g
Every custom action that modifies the machine is tied, directly or
indirectly, to a component. The compiler extension and schema make the
authoring be a child of Component
Use a different delimiter; the WiX CA's use EUR. I've been tempted to
use XML (just because it makes reading the logs so much easier -
probably overkill for anything short of serializing .NET objects)...
Thanks,
Thomas S. Trias
Senior Developer
Artizan Internet Services
I have examined the code some more and it follows the model Rob outline and
uses component state to determine what to do.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com
From: Richard [mailto:legal...@xmission.com]
Sean,
Creating the actual extensions to the compiler (candle), linker (light),
decompiler (dark), serializer / gatherer (heat), etc. requires a .NET
assembly; your choices there include managed C++ or a managed wrapper
around a native DLL.
That said, most of the extensions are coupled with
I tried adding the following custom action sequenced to happen after
MsiPublishAssemblies and even though the verbose logs show it completing
successfully the dll.config is not there after setup competes. Any thoughts
on why that is happening and how I get this required dll.config file placed
Yeah, right up there with advertised COM components. g/
Thomas S. Trias
Senior Developer
Artizan Internet Services
http://www.artizan.com/
Original Message
Subject: Re: [WiX-users] What keeps borking my ICE validation by
registeringVBScript and JScript under HKCU?
From:
Neil,
I've noticed that design pattern in the IIS extensions as well; their
modus operandi in the most recent WiX code I have is to include the
install state and install action of the related component as part of
their wrapped query data in the CustomActionData. I'm not sure the
reason
I'm trying to add a Condition to my WiX based installer to make sure that IE8
is installed on the machine. I used a RegistrySearch to find the appropriate
reg key with the currently installed version of IE. Unfortunately, it is in a
4-part form such as 8.0.6001.18372. I want to just grab the
In my install I need to have some sort of way to install about 15 .job
scheduled tasks. When I look at the tasks folder it looks like an
object and not a regular folder. Any ideas on how I would go about
copying them over?
Thanks,
Jim
That works; dark.exe can do it too.
Thomas S. Trias
Senior Developer
Artizan Internet Services
http://www.artizan.com/
Original Message
Subject: Re: [WiX-users] Files in an MSI
From: Jim Williams jimwilliam...@comcast.net
To: 'General discussion for Windows Installer XML
I've had to do something similar to this. Come Monday if you don't have any
leads I'll help ya.
On Fri, Feb 20, 2009 at 6:30 PM, Dan Giambalvo
danie...@windows.microsoft.com wrote:
I'm trying to add a Condition to my WiX based installer to make sure that
IE8 is installed on the machine. I
A GUID works nicely... :)
On Fri, Feb 20, 2009 at 6:10 PM, Thomas S. Trias tomtr...@artizan.comwrote:
Use a different delimiter; the WiX CA's use EUR. I've been tempted to
use XML (just because it makes reading the logs so much easier -
probably overkill for anything short of serializing
Essentially, what I'd like to do is to install one file in two folders.
We have one file called app.ico. It needs to be installed in
ProgramFiles\MyCompany\MyApp folder and ProgramFiles\MyCompany\MyApp\Images
folder. - Please don't ask me why, this is the requirement.
Anyways, I searched the
54 matches
Mail list logo
