]
Sent: 01 January 2011 20:30
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] problem with XmlConfig when migrating from Wix 3.0to
Wix 3.5
Looks like attachment does not work properly. Here are the two files that can
repro the problem.
Product.wxs
http
schemas.microsoft.com/wix/IIsExtension";>
- Original Message
From: Zhisheng Huang
To: General discussion for Windows Installer XML toolset.
Sent: Sat, January 1, 2011 11:43:29 AM
Subjec
et.
Sent: Sat, January 1, 2011 1:17:31 AM
Subject: Re: [WiX-users] problem with XmlConfig when migrating from Wix 3.0 to
Wix 3.5
Could you post the WiX you are using to do this edit.
Neil
-Original Message-
From: Zhisheng Huang [mailto:zhhuang5...@yahoo.com]
Sent: 01 January 2011 05:4
Could you post the WiX you are using to do this edit.
Neil
-Original Message-
From: Zhisheng Huang [mailto:zhhuang5...@yahoo.com]
Sent: 01 January 2011 05:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] problem with XmlConfig when migrating from Wix 3.0 to Wix
3.5
Hi,
I
Hi,
I have a Wix 3.0 project which installs an web application under default web
site, it also uses XmlConfig to modify the section of that web site in
applicationHost.config file. That works fine under Wix 3.0, however, after
migrating to Wix 3.5 it fails with following error.
ExecXmlConfig:
On 3/6/2010 12:04 PM, Richard Fine wrote:
> I don't see any. The same line in a later attempt:
> MSI (s) (48:A8) [20:04:24:913]: Executing op:
> ActionStart(Name=ExecXmlConfig,,)
> MSI (s) (48:A8) [20:04:24:914]: Executing op:
> CustomActionSchedule(Action=ExecXmlConfig,ActionType=3073,Source=Binar
On 05/03/2010 02:00, Bob Arnson wrote:
> On 3/4/2010 3:50 PM, Richard Fine wrote:
>
>> MSI (s) (48:34) [19:55:31:273]: Invoking remote custom action. DLL:
>> C:\Windows\Installer\MSIBFC7.tmp, Entrypoint: ExecXmlConfig
>>
>>
> What's after that line? There should be a bit of logging if it
On 3/4/2010 3:50 PM, Richard Fine wrote:
> MSI (s) (48:34) [19:55:31:273]: Invoking remote custom action. DLL:
> C:\Windows\Installer\MSIBFC7.tmp, Entrypoint: ExecXmlConfig
>
What's after that line? There should be a bit of logging if it couldn't
process an XmlConfig row.
--
sig://boB
http:
Hi,
I've got a package that is a plug-in for another product. When I install
the plug-in, I want it to modify the app.config file for the primary
product to register itself; similarly I want it to deregister itself on
uninstall. I've got this all working except for the uninstall part.
In my wx
Hi Stefan,
I had the same problem.
A simple but unpretty solution I found was to add a second step to populate
the empty namespace attribute. e.g.
http://add-your-toplevel-schema-namespace-here";
Sequence="2" />
Which results in
http://add-your-toplevel-schema-namespace-here"; />
L
ith XSL in MSXML.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Gauter
Sent: Thursday, April 17, 2008 07:30
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Problem with XMLConfig Element (empty xmlns attribute)
Hi,
When adding a new element to my web.config with XmlC
Hi,
When adding a new element to my web.config with XmlConfig I'll get an
empty xmlns attribute.
How can I suppress this xmlns attribute?
My Wix Code (using v3.0.3815):
Resulting in:
Possibly the standard xmlns attribute
(http://schemas.microsoft.com/.NetConfiguration/
12 matches
Mail list logo
