title: Unexpected end of file (#2034) in MVC/ASP .NET C# solution
body: <p>I'm calling a stored procedure and the result is in ISingleResult&lt;>...I created an xml document and then try to load the xml. I get an error on this line:</p>
  
  <pre><code>xml.LoadXml(airport.XML_F52E2B61_18A1_11d1_B105_00805F49916B);
  </code></pre>
  
  <p>The error says: <code>{"Unexpected end of file while parsing Name has occurred. Line 1, position 2034."}</code></p>
  
  <p>This is the XML it's returning ends like this:</p>
  
  <pre><code>&lt;EndTm&gt;2215&lt;/EndTm&gt; \n\t&lt;D"`
  </code></pre>
  
  <p>If I call the SP with the itineraryId and ItineraryItemId I get:</p>
  
  <pre><code>&lt;AirSegSellMods ItineraryItemID="1"&gt;
    ...
  &lt;/AirSegSellMods&gt;
  </code></pre>
  
  <p>It's as if visual studio is getting a truncated version of the XML. </p>
  
  <pre><code>foreach(ItineraryItems item in ItineraryItems) {
       if (item.SuperCategoryId == 4) {
  
          StoredProceduresDataContext airProc2 = new StoredProceduresDataContext();
  
          ISingleResult &lt; STOREDPROC&gt; airportsFromSalesId = airProc2.STOREDPROC(item.ItineraryId, item.ItineraryItemId);
  
          List &lt; AirItinerary &gt; listOfAir = new List &lt; AirItinerary &gt; ();
          foreach(STOREDPROC airport in airportsFromSalesId) {
              XmlDocument xml = new XmlDocument();
              xml.LoadXml(airport.XML_F52E2B61_18A1_11d1_B105_00805F49916B);
  
              XmlNodeList xnList = xml.SelectNodes("/AirSegSellMods/AirSegSell"); 
              foreach(XmlElement xn in xnList) {
  
                  listOfAir.Add(new AirItinerary() {
                      FltNum = xn.GetAttribute("FltNum"),
                      StartDt = xn.GetAttribute("StartDt"),
                      //...continued
                  });
              }
          }
          item.AirItems = listOfAir;
      }
  }
  </code></pre>
  
  <p>I have done something very similar to this before with no such problems. My coworker runs the exact same code and doesn't get this error so I think it's something specific to a visual studio setting.</p>
  
  <p>Any suggestions, thanks.</p>