Through inheritence a class can be more then one type and this is referred to as polymorphism. Within C# all types are polymorphic, because it treats every type as an Object.

The Microsoft definition is as follows:
“Through inheritance, a class can be used as more than one type; it can be used as its own type, any base types, or any interface type if it implements interfaces. This is called polymorphism. In C#, every type is polymorphic. Types can be used as their own type or as a Object instance, because any type automatically treats Object as a base type.

Polymorphism is important not only to the derived classes, but to the base classes as well. Anyone using the base class could, in fact, be using an object of the derived class that has been cast to the base class type. Designers of a base class can anticipate the aspects of their base class that are likely to change for a derived type. For example, a base class for cars might contain behavior that is subject to change when the car in question is a minivan or a convertible. A base class can mark those class members as virtual, allowing derived classes representing convertibles and minivans to override that behavior.”

The basic “meaning” by the above statement is all C# types are derived from System.Object which allows them to be “morphed” into any type.

 

This error is cause by the the clientBaseAddress URI not having elevated premission to create the listener port in IIS.

To fix this issue by using identity impersonation and add/update the follow web.config keys:

<identity impersonate="true" />

Then you can configure impersonation any way you would like.

 

I ran into a small issue using an XML document type in SQL 2005 from BizTalk 2006 R2 and it turn our to be a namespace pass in from the sp_xml_preparedocument statement in my stored procedure.

You need to set it up as follows:
EXECUTE sp_xml_preparedocument @idoc OUTPUT, @xmlMessage, ‘<root xmlns:ns1=”http://namespacename” />’

The ‘<root xmlns:ns1=”http://namespacename” />’ being the most important part as this defines the namespace from the first part of your message.

Then your OPENXML call can be set up using the namespace – i.e /ns1:<node> etc.

 

Microsoft BizTalk Server 2006 Working with Schemas lab is available at the following link:

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032296903&EventCategory=3&culture=en-US&CountryCode=US

* Requires Registration

 

Microsoft has released BizTalk 2006 for SAP labs, these labs are available for downloading at:

http://www.microsoft.com/downloads/details.aspx?FamilyID=49d09411-2211-4549-9de8-ff3a136202d1&DisplayLang=en

© 2011 Greg Leonardo Suffusion theme by Sayontan Sinha
show
 
close