c# Archives - gordon.byers.me

I’m in the midst of putting together a few Azure Functions to use with Logic Apps.
This one is pretty simple, and demonstrates a couple of concepts so I thought I’d share.

{
  "bindings": [
    {
      "name": "req",
      "type": "httpTrigger",
      "direction": "in",
      "webHookType": "genericJson"
    },
    {
      "name": "res",
      "type": "http",
      "direction": "out"
    }
  ],
  "disabled": false
}

{

"bindings": [

{

"name": "req",

"type": "httpTrigger",

"direction": "in",

"webHookType": "genericJson"

{

"name": "res",

"type": "http",

"direction": "out"

}

"disabled": false

}

#r "Newtonsoft.Json"

using System;
using System.Net;
using System.Xml;
using Newtonsoft.Json;

public static async Task<HttpResponseMessage> Run(HttpRequestMessage req, TraceWriter log)
{
    log.Info($"C# HTTP trigger function processed a request. RequestUri={req.RequestUri}");

    string jsondoc = await req.Content.ReadAsStringAsync();
    
    if (jsondoc == null ) {
        return req.CreateResponse(HttpStatusCode.BadRequest, new {
            error = "Please post JsonDoc"
        });
    }
    else {
        try {
            //dynamic data = JsonConvert.DeserializeObject(jsondoc);
            //log.Info($"{data.ModuleHeader.SignOnDate}");
            
            //create root
            
            XmlDocument xDoc = JsonConvert.DeserializeXmlNode(jsondoc, "newrootnode");
            log.Info($"{xDoc.OuterXml}");
            
            
            
            return req.CreateResponse(HttpStatusCode.OK, xDoc.OuterXml);
             
        }
        catch(Exception ex){
            log.Info($"{ex.ToString()}");
                    return req.CreateResponse(HttpStatusCode.BadRequest, new {
            error = $"Error parsing jsondocument {ex.Message}"
            });
        }
    }
}

#r "Newtonsoft.Json"

using System;

using System.Net;

using System.Xml;

using Newtonsoft.Json;

public static async Task<HttpResponseMessage> Run(HttpRequestMessage req, TraceWriter log)

{

log.Info($"C# HTTP trigger function processed a request. RequestUri={req.RequestUri}");

string jsondoc = await req.Content.ReadAsStringAsync();

if (jsondoc == null ) {

return req.CreateResponse(HttpStatusCode.BadRequest, new {

error = "Please post JsonDoc"

});

}

else {

try {

//dynamic data = JsonConvert.DeserializeObject(jsondoc);

//log.Info($"{data.ModuleHeader.SignOnDate}");

//create root

XmlDocument xDoc = JsonConvert.DeserializeXmlNode(jsondoc, "newrootnode");

log.Info($"{xDoc.OuterXml}");

return req.CreateResponse(HttpStatusCode.OK, xDoc.OuterXml);

}

catch(Exception ex){

log.Info($"{ex.ToString()}");

return req.CreateResponse(HttpStatusCode.BadRequest, new {

error = $"Error parsing jsondocument {ex.Message}"

});

}

{
  "frameworks": {
    "net46": {
      "dependencies": {
        "Newtonsoft.Json": "9.0.1"
      }
    }
  }
}

{

"frameworks": {

"net46": {

"dependencies": {

"Newtonsoft.Json": "9.0.1"

}

gord

Cloud Solution Architect at Microsoft in the UK.

http://gordon.byers.me

Came across this issue for the 2nd time, so thought it was worth writing about since google doesn’t really turn up much.

I’d written a .NET4 c# console app that connects to Salesforce’s API and queries for specific record entities that have been modified. The console app was set to compile for Any CPU and was always running x64 on my laptop and the server. I extended the application to query the Salesforce Opportunity entity, which worked fine on the laptop but not on the server (Microsoft Windows Server 2008 R2 Standard).

The server returned the following error;
System.InvalidOperationException: There is an error in XML document (1, 3739). ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

So it was obviously a machine specific issue, since it worked on my laptop (and another server). But there really wasn’t much else to help, so troubleshooting then begins.
The end result is that it transpires running the console app as complied x86 only (forcing 32 bit running) fixes the issues.

Hope this helps someone.

gord

Cloud Solution Architect at Microsoft in the UK.

http://gordon.byers.me

Tag: c#

Azure Functions – Convert Json to Xml with newtonsoft

Salesforce API .NET exception – a strange one