Errors in .NET proxy class generation and its WSDL in BizTalk
When a proxy class is generated with BizTalk 2004 and 2006 (not R2 as it seems) it will hold a few errors. It's important to take these irregularities into account (Microsoft calls it "by design").
Mandatory strings (minoccurs="1") are converted to optional (minoccurs="0"). Nullable types (xsi:nil="true"), e.g. xs:int or xs:datetime, are ignored when passing it through the proxy class.
I could try and explain the problem, though the entire "problem" can be found on the URL below. This is a Microsoft source.
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=101972
Mandatory strings (minoccurs="1") are converted to optional (minoccurs="0"). Nullable types (xsi:nil="true"), e.g. xs:int or xs:datetime, are ignored when passing it through the proxy class.
I could try and explain the problem, though the entire "problem" can be found on the URL below. This is a Microsoft source.
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=101972
Labels: asmx, biztalk, generation, issue, microsoft, minoccurs="0", minoccurs="1", nillable, nullable, proxy class, types, WSDL, xs:int, xs:string, xsi:nil


0 Comments:
Post a Comment
<< Home