Skip to main content

Serialized headaches when you combine .NET Core and .NET 4.6

When I'm involved in an application development project, I try all the time to keep the language ecosystem reduced as much as possible. Even if we are leaving in a world where interoperability is higher than ever, there are times when because of this you can lose a lot of time because of it.

Let's take the below example:
  • An Azure Function application wrote in .NET 4.6 that send messages to Azure Service Bus Topic. Inside the message body content is serialized in JSON format
  • An Azure Web App application wrote in .NET Core that receives messages from Azure Service Topic and displays it on the UI.

Everything it is okay until you run the code and an error occurs during deserialization. When you take a look at what you send and receive you see the following:

.NET 4.6 OUTPUT:       @ string 3�k{"CountryCode":"RO","AlertType":0,"Level":5,"ValidFrom":"2018-04-05T10:14:00.0458475Z","Period":"00:02:00"}
.NET Core EXPECT:    {"CountryCode":"RO","AlertType":0,"Level":5,"ValidFrom":"2018-04-05T10:14:00.0458475Z","Period":"00:02:00"}

Both implementations are using Newtonsoft library for content serialization and deserialization, but it seems that the behavior is different.

.NET 4.6 Sample
string jsonWeatherAlert = JsonConvert.SerializeObject(weatherAlert);
BrokeredMessage message = new BrokeredMessage(jsonWeatherAlert);
message.Properties.Add("countrycode", weatherAlert.CountryCode);
.NET Core Sample
string bytesAsString = Encoding.UTF8.GetString(message.Body);
WeatherAlert alert = JsonConvert.DeserializeObject<WeatherAlert>(bytesAsString);

The root cause of this problem is related to what kind of default serializer it is used behind the scene. One of them it is using DataContract and bytes directly from the stream VS the other one that it is using DataContractBinarySerializer and GetBody<Streeam> to load all bytes.
This difference has a direct impact not only on the Newtonsoft library but also to Service Bus library if you want to use it directly.

To solve the problem you need on the sender or received to change the default serializer library that it is used. In our case, we updated the .NET 4.6 implementation in the following way.
var jsonSerializar = new DataContractJsonSerializer(typeof(WeatherAlert)); 
BrokeredMessage message = new BrokeredMessage(weatherAlert, jsonSerializar); 
message.Properties.Add("countrycode", weatherAlert.CountryCode); topicClient.Send(message);

If you want to find more about it, I invite you to read the following link discussion


Popular posts from this blog

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 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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.