Since I've had four people correct me already, I did *mean* "Managed
CustomActions are *not* supported by the Windows Installer."
Sorry for the spam...
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: Wednesday, October 11, 2006 3:22 P
Personally, I think that is not good advice.
In all the time I've spent writing CustomActions the only robust solution is to
have a simple native DLL with as few dependencies as possible. Exe
CustomActions can't provide progress or data back to the install. The
Installer class is just another
Managed CustomActions are supported by the Windows Installer. You can do lots
of things to try and wire in PInvoke and loading the CLR in a hosted situation
but there are real concerns about how those types of CustomActions can affect
your install scenarios... especially if you install anything
Two ways. One is to create a console application, and use wix's custom tag to
call it during execution, passing flags as necessary.
Two is to inherit from the Installer class. I'm not sure how you get that code
hooked up using Wix, though. Sorry I can't be more help here.
-Original Messa
I'd like to be able to do the following during an upgrade:
1.) Before InstallFiles, determine if my service (from a previous
install) is up;
2.) If it is not up, start it;
3.) Query the service (this part I'll use a custom action for), the
end result is setting some properties
4.) Stop the se
>
> Also, since the machines you're installing on have the .net
> runtime installed (or else there wouldn't be a machine.config
> to edit), you could write a .NET custom action (easier than
> c++) that runs before XMLFile, and performs your xml search
> on machine.config, and sets a property t
Rob,
You said "Managed CustomActions aren't supported either". Is that with
version 3.0? I'm using WIX version 2.0.4415.0 because I need to be
ready very soon and I don't want to deal with the [potential] changes.
Would managed CAs be OK for WiX V2.0?
__
Doug Wat
VBScript has lots of issues (you can see my blog about that). Managed
CustomActions aren't supported either.
I think K just checked in an improved XmlFile CustomAction called XmlConfig
that handles more complex changes to XML files than what XmlFile supports. I
expect it is only in the latest
I'm not really sure about sending properties back from managed code. Worst
case, you could do all your machine.config changes in the mgd code CA.
I think you'll hear some complaints from this alias if you use vbscript to
create a custom action. The problem is that supporting reinstall and roll
Thanks guys.
David: The application is already written (it's been in production for a
couple of years). So changing the way it uses machine.config is not an
immediate option. Your suggestion would actually be my preferred way.
Cullen: I'm actually looking into writing a VB script to run as a cu
Also, since the machines you're installing on have the .net runtime installed
(or else there wouldn't be a machine.config to edit), you could write a .NET
custom action (easier than c++) that runs before XMLFile, and performs your xml
search on machine.config, and sets a property telling XmlFile
Not sure if this helps Douglas, but could you add a custom section and
section handler instead of using AppSettings? That way, you are assured
that the section would not exist prior to you adding it and you are not
limited to using duplicate key names since your configuration section
handler c
I'm using a custom action that accesses the INSTALLDIR directory, and thus
it must run after the directory is created. I do it like this :
This works fine, except it runs on uninstall as well. So I try :
NOT Installed
Now, that does NOT work, and I suspect it may be because [Installed
I tried that but I get an error basically
saying that the appSettings node could not be found. The problem gets more
complicated in that if the appSettings element already exists and contains
child elements ( elements) then I risk overwriting them. Apparently
WiX (at least 2.0.4415) does
I don’t have a definite solution, Doug, but I have a
suggestion. Have you tried just creating your elements, without
specifying the element, in a machine.config that doesn’t
contain the ? Maybe the XmlFile element is smart enough to
create the path if your XPath doesn’t exist.
F
Hi,
I am newbie to WiX and I have two quick questions.
1)
I have a deferred custom action that runs at the end of
an installation. I want to change the text displayed in my exit dialog
depending on the results of the custom Action. Usually, I would do this using
properties but t
Jarrod Albert wrote:
> Any help would be greatly appreciated. The directory where
> WixIIsExtension.dll is located is in by path, and I even tried included the
> whole path for the -ext option and I still got the same error.
>
Extensions need to be in the same directory as candle.exe, light.e
Joseph Barkley wrote:
> I need to parse an xml file that is being installed with my current
> project. I'd like to keep the code for the parsing inside of the
> component for the xml file, but it simply will not use the [#fileId]
> properly. It compiles and runs, but it errors out because it doe
Peterson, Joel wrote:
I’m not looking
for any
dialogs in particular, but sometimes you don’t know what you can use
until you see it. I’ve implemented my own, and was curious what others
have done with WiX UI and also if there was a cookie-cutter wizard
template
that we should be
BULL, Dave, GBM wrote:
> If blah.dll is a .NET assembly then it works fine, but if it's a regular DLL
> or even an empty file then I get the message.
>
What's your authoring look like? Light looks inside .NET assemblies to
get version info but only if you marked the file as a .NET assembly.
Simon Burgess wrote:
Thanks Bob,
do you have an idea of the
syntax needed were I to do that as obviously here the value of one
property is
required for the DirectorySearch’s path
So the DirectorySearch picks up the value from RegistrySearch as the
start path.
Frank Tse wrote:
In
any case, I did enter a feature request for the ngen action optionally
not to fail setup when it encounters error.
Rob pointed out that in recent v2 weekly builds, that feature is
already implemented. Take a look at today's build.
--
sig://boB
http://b
Wilson, Phil wrote:
There is the FileVersion way to do an in-place
update of a GAC assembly. Last bullet here:
I think the scenario is a user who already GAC'd an assembly with the
same assembly and file versions.
--
sig://boB
http://bobs.org
-
There's a list here:
http://installsite.org/pages/en/msi/books.htm
Knowing German would be helpful looking at that
list
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peterson,
JoelSent: Wednesday, October 11, 2006 9:18 AMTo:
wix-users@lists.sourceforge.n
every compiler and linker is probably at the mercy of Visual
Studio’s environment variables
I think that's probably an accurate assessment. Take a look at the
documentation for the Win32 CreateProcess function. There's a
parameter (lpEnvironment) that let's the calling process customize the
Hi all.
Are there any decent books on the core architecture of
Windows Installer and MSI (seriously, there are enough books on InstallShield)?
I feel that having a deep understanding on the Windows Installer architecture would
give me a better foundation in knowing what I should and sho
I've fixed the problem by adding the -sa switch to Light.exe. Question is,
why do I have to do this on one machine but not the other?
Dave
>> error LGHT0132 : The assembly file 'blah.dll' appears to be invalid.
Please ensure this
>> is a valid assembly file and that the user has the appropriate a
Hi
Following my last post on the 15th September, I am still having this
problem.
I'm using version 3.0.2015.0 of Wix and am getting the following message
when I light the wixobj:
error LGHT0132 : The assembly file 'blah.dll' appears to be invalid. Please
ensure this is a valid assembly file and
I am working on changing my WiX 2.0 files to 3.0. So far it has been going
well. However, one of my wxs files does some web things that have been
moved to an extension file. I changed my wxs file to include
xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension"; and put iis: on
the front
I need to parse an xml file that is being installed with my current project. I'd like to keep the code for the parsing inside of the component for the xml file, but it simply will not use the [#fileId] properly. It compiles and runs, but it errors out because it doesn't resolve [#fileId] during the
Does anyone know how to check for the existence
of a particular element in an XML file? I need to add to
the machine.config file but if I assume that the node does
not exist then I end up with two. The only thing I see in the WiX schema is
XmlFile which creates or updates elements. I n
INTEGRATE SHIPPING LIMITED Rm 31D, 24C,Qiaoyuan Mansion, #750 Xizhang South Rd., 200011 Shanghai,ChinaTel：86-21-63459257,63450332,63456109 Fax：86-21-63456292,63450279[EMAIL PROTECTED]WEB:http://www.islcn.com Dear Sir/Lady ,Below freshed rate update iss
32 matches
Mail list logo
