I guess wixcop doesn't update extension elements for you.
These errors are coming because all these elements have all been moved into
extensions of the wix toolset. Use wix.chm to see which element is part of
which extension. Then make sure you reference the appropriate extensions'
namespace in your Wix element. For example, here's how to include the util
namespace:
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
Then to reference it appropriately, change:
<XmlFile>
To
<util:XmlFile>
WebDirProperties is part of IIS, etc. Then during both compile and link, you
need to reference the right extension too when compiling, like:
Candle -ext wixutilextension <allyourothercandleargs> file.wxs
Light -ext wixutilextension <allyourotherlightargs> file.wixobj
Hopefully you get the idea.
Thanks,
Mike Carlson
-----Original Message-----
From: Navid Azimi-Garakani
Sent: Tuesday, March 16, 2010 1:36 PM
To: Mike Carlson (DEV DIV); General discussion for Windows Installer XML
toolset.
Subject: RE: WIX 2.0 on IIS 7.5 with IIS 6.0 Compatiblity Mode
Thanks again. Running WixCop will help a lot but I am still having trouble
solving these errors:
1>src\setup\common\common.wxi(15) : error CNDL0005 : The Product element
contains an unexpected child element 'WebDirProperties'.
1>src\setup\common\common.wxi(18) : error CNDL0005 : The Product element
contains an unexpected child element 'WebApplication'.
1>src\setup\common\common.wxi(27) : error CNDL0005 : The Product element
contains an unexpected child element 'Group'.
1>src\setup\common\common.wxi(3427) : error CNDL0005 : The Component element
contains an unexpected child element 'WebSite'.
1>src\setup\common\common.wxi(3442) : error CNDL0005 : The Component element
contains an unexpected child element 'WebVirtualDir'.
1>src\setup\common\common.wxi(3557) : error CNDL0005 : The Component element
contains an unexpected child element 'XmlFile'.
I do not even know what the right thing to do is for them. I could automate it
if I knew what they should be instead. Any ideas?
Thanks,
Navid
-----Original Message-----
From: Mike Carlson (DEV DIV)
Sent: Tuesday, March 16, 2010 9:54 AM
To: Navid Azimi-Garakani; General discussion for Windows Installer XML toolset.
Subject: RE: WIX 2.0 on IIS 7.5 with IIS 6.0 Compatiblity Mode
I forgot to mention, running "wixcop -f" on your authoring files should
automatically update your files from any schema changes from WiX 2.0 to WiX 3.0.
I can't guarantee it will fix everything, but it should fix a lot of trivial
things for you.
-----Original Message-----
From: Navid Azimi-Garakani
Sent: Monday, March 15, 2010 8:34 PM
To: General discussion for Windows Installer XML toolset.
Cc: Mike Carlson (DEV DIV)
Subject: RE: WIX 2.0 on IIS 7.5 with IIS 6.0 Compatiblity Mode
I should mention that that errors are primarily trivial with the exception of
the following:
1>src\setup\common\common.wxi(15) : error CNDL0005 : The Product element
contains an unexpected child element 'WebDirProperties'.
1>src\setup\common\common.wxi(18) : error CNDL0005 : The Product element
contains an unexpected child element 'WebApplication'.
1>src\setup\common\common.wxi(27) : error CNDL0005 : The Product element
contains an unexpected child element 'Group'.
1>src\setup\common\common.wxi(3427) : error CNDL0005 : The Component element
contains an unexpected child element 'WebSite'.
1>src\setup\common\common.wxi(3442) : error CNDL0005 : The Component element
contains an unexpected child element 'WebVirtualDir'.
1>src\setup\common\common.wxi(3557) : error CNDL0005 : The Component element
contains an unexpected child element 'XmlFile'.
These occur 500+ times. Does anyone have any documentation about migrating from
WiX 2.0 to WiX 3.0? It looks like the schema is not backwards compatible.
Thanks!
Navid
-----Original Message-----
From: Navid Azimi-Garakani
Sent: Monday, March 15, 2010 6:35 PM
To: General discussion for Windows Installer XML toolset.
Cc: Mike Carlson (DEV DIV)
Subject: RE: WIX 2.0 on IIS 7.5 with IIS 6.0 Compatiblity Mode
Thanks Mike!
I gave WiX 3.0.5329.0 a try but ended up with literally thousands of
warnings/errors. I am planning on rewriting our entire setup (by migrating it
to MSBuild) so going through and fixing all these errors is a nonstarter. I
need to provide a solution for this current release. The rewrite is scheduled
for our next release.
With this in mind, do you know if there are any convertors available for
migrating WiX v2.0 .wxs files to be WiX v3.0 compatible? There are some easy
problems (e.g. namespace needs to be updated) but I am getting builds errors
saying that
I am currently doing a private build with 2.0.5508.0 (instead of 2.0.3719.0) to
see if this resolves the blocking issues. If not, I'm going to see if upgrading
to WiX v3.0 would even solve the issue before worrying about the migration.
Thanks,
Navid
-----Original Message-----
From: Mike Carlson (DEV DIV) [mailto:[email protected]]
Sent: Monday, March 15, 2010 2:59 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WIX 2.0 on IIS 7.5 with IIS 6.0 Compatiblity Mode
I don't know what would cause this issue in 2.0, but have you considered
upgrading to WiX 3.0 or even WiX 3.5?
A *huge* number of improvements have gone into WiX's IIS support in the WiX 3.0
RTM release. Going even further, WiX 3.5 actually has native support for IIS7,
so it doesn't require the IIS6 compatibility layer (but 3.5 is still under
development, so expect some bugs if you try 3.5).
Thanks,
Mike Carlson
-----Original Message-----
From: Navid Azimi-Garakani [mailto:[email protected]]
Sent: Monday, March 15, 2010 2:29 PM
To: [email protected]
Subject: [WiX-users] WIX 2.0 on IIS 7.5 with IIS 6.0 Compatiblity Mode
I am having an issue deploying to IIS 7.5 on Windows Server 2008 R2 using WIX
2.0.3719.0 with IIS 6.0 Compatibility Mode. The problem is that anytime we
deploy a virtual directory it "destroys" the parent site. To clarify, the
virtual directory gets installed correctly but the parent site no longer has a
physical path or application pool associated with it.
We have two separate MSIs: one to install the parent site and one to install
the virtual directory. Has anyone ever run into this? Or have any ideas on what
I can do to debug this further? The same MSIs work perfectly on IIS 6.0 running
on Windows Server 2003.
Any help would be massively appreciated.
Thanks,
Navid
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune applications
for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune applications
for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
