Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: "The InnerText property is write only" error message when you use System.Xml.XmlDocument in BizTalk Server 2010 or in BizTalk Server 2013


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You create a new Microsoft BizTalk Server 2010 or in Microsoft BizTalk Server 2013 project in Microsoft Visual Studio 2010.
  • You create one orchestration to the project.
  • You create the following two variables in the orchestration:
    • var1: System.Xml.XmlDocument
    • var2: System.String
  • You add one expression shape to the orchestration.
  • You add the following code to the expression shape:
    var1 = new System.Xml.XmlDocument(); var2 = var1.InnerText; 
In this scenario, you receive the following error message:
'var1.InnerText': .NET property is write-only because it does not have a get accessor.

↑ Back to the top


Resolution

Cumulative update information

For BizTalk Server 2013

The hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2013.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2892599 Cumulative update package 2 for BizTalk Server 2013

For BizTalk Server 2010

The hotfix that resolves this issue is included in cumulative update package for BizTalk Server 2010.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2855367 Cumulative update package 6 for BizTalk Server 2010

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Workaround

To work around the issue, redefine the XmlDocument as XmlNode.

↑ Back to the top


Keywords: kb, kbqfe, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2835689
Revision : 1
Created on : 1/7/2017
Published on : 10/31/2013
Exists online : False
Views : 386