Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Submitted By: Ilya Konstantinov (ikonst)
>Assigned to: Derek (derekc)
Summary: Add dependency on .NET 1.1 SP1
Recently I've been debugging a rather ugly bug. It was
an exception that began appearing suddenly (after some
editing to the .wxs file) and disappeared as soon as I
shuffled components, changed spacing etc.
Looking at the sources, it was a System.Xml error while
parsing WiX' internally-generated XML data (the one
with the <?ln ...?> processing instructions...).
I extracted the internally-generated XML data and
verified it with my own simple System.Xml-based loader.
System.Xml was making incorrect Parsing Error
accusations (which neither MSXML4 nor libxml made, and
which I couldn't make either after looking at the
file). Changing a space here and there in the file
seemed to make the parsing problem go away, suggesting
it's some ugly bug in the System.Xml implementation.
Luckily, after upgrading my .NET Framework 1.1 to
Service Pack 1, this problem went away, suggesting this
System.Xml bug was fixed.
Could we make SP1 a dependency (via manifest settings
or otherwise) of WiX so other users would save their
time banging their heads against the wall with this bug?
It's unfortunately not possible to create a dependency upon
service pack specific versions of a framework assembly.
However, I've submitted for review a fix that would catch
the most common scenario in which this bug manifests itself
and displays a notice directing the user to download SP1.
This should be sufficient for helping future users avoid the
pain you went through.