NDoc failure with 2005 GA   

Hi

I'm using NDoc 1.3.1 to build .HxS and .chm files from VS .NET 2005
assemblies (using a config file to set the supportedRuntime version to
v2.0.50727). It was working well during the .NET beta, but when we
switched from the .NET beta build to the GA build, NDoc started failing
when it reached the sixth topic in the file with the following error:

Generating HTML...
ndocSybaseDataWindowWeb_90235722.html
ndocSybaseDataWindowWebHierarchy_90235722.html
ndocSybaseDataWindowWebAfterPerformActionEventArgsClassTopic_857bee76.html
ndocSybaseDataWindowWebAfterPerformActionEventArgsClassMembersTopic_857bee76.html
ndocSybaseDataWindowWebAfterPerformActionEventArgsClassPropertiesTopic_857bee76.html
ndocSybaseDataWindowWebAfterPerformActionEventArgsClassActionTopic_4f1189e2.html
Error: NDoc.Core.DocumenterException
An error occured while creating the documentation
Error: System.Xml.XPath.XPathException
Expression must evaluate to a node-set.

   at
NDoc.Documenter.NativeHtmlHelp2.NativeHtmlHelp2Documenter.Build(Project
project)
   at NDoc.ConsoleApplication.EntryPoint.Main(String[] args)
Error: NDoc.Core.DocumenterException
An error occured while creating the documentation
Error: System.Xml.XPath.XPathException
Expression must evaluate to a node-set.

   at
NDoc.Documenter.NativeHtmlHelp2.NativeHtmlHelp2Documenter.Build(Project
project)
   at NDoc.ConsoleApplication.EntryPoint.Main(String[] args)

I have tried this on two separate assemblies, and modified the comments
file to exclude the topics on which the failure occurred, but it always
fails on the sixth topic, whatever its content. The CHM build runs to
completion. Does anyone have any suggestions?

Thanks
Marilyn

date: 1 Dec 2005 12:08:23 -0800   author:   unknown

Re: NDoc failure with 2005 GA   

I'm using the same build of NDoc you are with .NET 2.0 assemblies and
having problems generating VS.NET documentation.  Same XPathException
as yourself.

For me it dies somewhere deep in the internal Microsoft XML processing
lib and always dies on the first Property (sorted alphabetically)
encountered in the assembly.  Other methods etc. seem to process fine.

Stack trace:

MS.Internal.Xml.XPath.ExtensionQuery.Advance()
MS.Internal.Xml.XPath.AttributeQuery.Advance()
MS.Internal.Xml.XPath.BooleanFunctions.toBoolean(XPathNodeIterator
nodeIterator)
MS.Internal.Xml.XPath.BooleanFunctions.Evaluate(XPathNodeIterator
nodeIterator) System.Xml.Xsl.XsltOld.Processor.Evaluate(ActionFrame
context, Int32 key)
System.Xml.Xsl.XsltOld.Processor.EvaluateBoolean(ActionFrame context,
Int32 key) System.Xml.Xsl.XsltOld.IfAction.Execute(Processor processor,
ActionFrame frame) System.Xml.Xsl.XsltOld.ActionFrame.Execute(Processor
processor)
System.Xml.Xsl.XsltOld.Processor.Execute()
System.Xml.Xsl.XsltOld.Processor.Execute(TextWriter writer)
System.Xml.Xsl.XslTransform.Transform(XPathNavigator input,
XsltArgumentList args, TextWriter output, XmlResolver resolver)
System.Xml.Xsl.XslTransform.Transform(IXPathNavigable input,
XsltArgumentList args, TextWriter output, XmlResolver resolver)
NDoc.Documenter.NativeHtmlHelp2.Engine.HtmlFactory.TransformAndWriteResult(String
transformName, String fileName) in
\\src\\Documenter\\NativeHtmlHelp2\\Engine\\HtmlFactory.cs:line 289

date: 13 Dec 2005 09:11:48 -0800   author:   unknown