News

Statistics

Locations of visitors to this page

Personal

June 2008 Entries

XmlDocument orchestration parameter: UnderlyingXmlDocument error


If you have an orchestration  that receives an XmlDocument parameter, when you call it from another orchestration, you will receive a compile error regarding UnderlyingXmlDocument.

The problem is that Biztalk can not use XmlDocument since it is not serializable, so Biztalk wraps it in another type called Microsoft.XLANGs.RuntimeTypes.XmlDocumentSerializationProxy. So basically you have to use this type instead of XmlDocument.

Here you can find all the details of the process, on Martin's blog (a great source of inspiration) :

http://martijnh.blogspot.com/2005_04_01_archive.html

 

posted @ Tuesday, June 24, 2008 6:57 AM | Feedback (0) |


A cause and its resolution for Unknown Server Tag ' < TagName > ' error


I am currently working on a project which keeps the code behind for aspx pages and controls in a different project, which is added as a reference to the Website project. I added some controls and variables on a page, let's call it Fees.aspx. Suddenly the website did not compile anymore because of an error in a page that had a reference to Fees.aspx error :
Unknown server tag ...
In the Fees.aspx the first line,
<%@ Control Language="C#" ClassName="Fees" Inherits="DllsRepository.FeesControl" %>
was undelined and there was warning saying that there is an "Ambiguous match ... "
I took the modifications one by one and finally I realised that in the code behind I had a string variable with the same name (but upper case) as one of the added controls. In C# there was no error, since C# is case sensitive, but in asp, that was a problem.
I renamed the variable and everything was fine afterwards.

posted @ Thursday, June 12, 2008 10:28 PM | Feedback (0) |