Skip to main content

Http Request in .NET Compact Edition ended with "Unable to read data from the transport connection … Unknown error (0x0)"

We are leaving in a world that begin to be dominates by smart devices – device2device communication is not something new. Today I would like tack about a problems that we had when we integrated 2 smart devices.
One of the devices expose an HTTP endpoint that can be used to communicate with him. Based on a REST API you can send to him different requests. From our desktops all the communication worked perfectly with this device.
When we imported the client code to a Smart Device Project (special project used to write components for Windows Compact Edition and .NET Compact Framework 3.5) we had a big surprise. Each HTTP request to the first device ended with the following error code:
“Unable to read data from the transport connection … Unknown error (0x0)”
…
at System.Net.HttpWebRequest.finishGetResponse()
at System.Net.HttpWebRequest.GetResponse()…
> The code that generated the error code was:
        public void SetColor(Color color)
        {
            if (color != Color.Red
                && color != Color.Green)
            {
                throw new ArgumentException("Color is not supported", "color");
            }
            try
            {
                byte[] messageContent = UTF8Encoding.UTF8.GetBytes(string.Format(MessageBody,
                    color == Color.Red ? RedCode : GreenCode));
                WebRequest request = WebRequest.Create(new Uri(
                                        string.Format("http://{0}/api/{1}/lights/{2}/state",
                                        ConfigurationManager.AppSettings["hueIP"],
                                        ConfigurationManager.AppSettings["hueUser"],
                                        ConfigurationManager.AppSettings["hueNumber"])));
                request.Method = "Put";
                request.Timeout = 10000;
                request.ContentType = "application/json";
                request.ContentLength = messageContent.Length;
                using (Stream stream = request.GetRequestStream())
                {
                    stream.Write(messageContent, 0, messageContent.Length);
                }
            }
            catch (Exception ex)
            {
                Trace.TraceError(ex.Message);
            }
        }
Because we use HttpWebRequest we expected to have a same a similar behavior with “normal” .NET, but it seems that this is not true. When you are working in “normal” .NET a part of the requests method string is automatically converted to UpperCase. In the moment when a request is made, the request method “Put” is converted to “PUT”. But, in a Smart Device project this is not happening – because of code optimization. So you end up with an HTTP request that has the method set to “Put”.
In general, the system will not have any kind of problems with this, because will know how to handle a request method written CamelCase.  In our case the second smart device it seems that cheeks the request method only with PUT written UpperCase.
In conclusion, when you work with a specific protocol, I recommend to always use the exact specification of the protocol and don’t assume that different stacked will make your job for you.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…