james.newtonking.comJames Newton-King

Blog Bio Follow Mar 31 2020 Introducing gRPC HTTP API gRPC is a modern way to communicate between apps. gRPC uses HTTP/2, streaming, Protobuf and message contracts to create high-performance, realtime services. Support for gRPC on ASP.NET Core was added in .NET Core 3.0 . The catch with gRPC is not every platform can use it. Browsers don’t fully support HTTP/2, making REST and JSON still the primary way to get data into . A good scenario to use gRPC HTTP API is building new services using gRPC and JSON. Q: How is this different than gRPC-Web? A: gRPC-Web lets you call gRPC services from the browser with the gRPC-Web client and Protobuf. gRPC HTTP API allows you to call your services as if they were RESTful APIs with JSON. It doesn’t replace gRPC-Web. Q: When will this be released? A: A pre-release package is on NuGet right now ! gRPC HTTP API is an experiment and the decision to invest more time on it depends on user feedback. Try it today! gRPC HTTP API is a framework idea that I have been playing around with. It is very experimental, but I think it has the opportunity for .NET developers to offer gRPC and REST services much faster than they can today. GrpcHttpApi @ aspnet/AspLabs repository on GitHub - Source code and instructions Microsoft.AspNetCore.Grpc.HttpApi package on NuGet.org - Pre-release package You can use the pre-release package on NuGet now. Whether more time is invested in making it a supported product depends on user feedback. Give feedback on GitHub or contact me @JamesNK on Twitter. I’m looking forward to seeing how this framework is used. Tweet Nov 27 2018 Json.NET 12.0 Release 1 - .NET Foundation, NuGet and Authenticode signing, SourceLink and more .NET Foundation Json.NET has joined the .NET Foundation! The .NET Foundation is an independent organization dedicated to fostering the .NET open source community. The .NET Foundation provides technical and legal guidance .NET open source projects. Joining the .NET Foundation ensures that Json.NET stays open and supported into the future. Read more on the .NET Foundation blog . NuGet package and Authenticode signing Json.NET 12 is the first release to sign the *.nupkg using NuGet package signing and sign the assembly files using Authenticode . Although it isn’t a common request, some users of Json.NET have asked for signed binaries because of company policy. This feature is made possible by the .NET Foundation, who offer code signing certificates and a signing service to member projects. Better debugging with SourceLink SourceLink is an neat technology that links a library to its source code. Originally created in the community by @ctaggart , SourceLink has been adopted by Microsoft and is supported in Visual Studio. This release adds SourceLink support to Json.NET, making it possible to step into the Json.NET source code as you debug your application. And lots more JSON Path supports JavaScript’s strict equality operators (=== & !==), StringEnumConverter can use a NamingStrategy and is faster, JavaScriptDateTimeConverter supports JavaScript date constructors with multiple arguments, there is a new option on JsonMergeSettings for case insensitive merging of property names, serializing SpanT properties no longer errors, and dozens of other new features and bug fixes. Changes Here is a complete list of what has changed since Json.NET 11.0 Release 2. New feature - Added NuGet package signing New feature - Added Authenticode assembly signing New feature - Added SourceLink support New feature - Added constructors to StringEnumConverter for setting AllowIntegerValue New feature - Added JsonNameTable and JsonTextReader.PropertyNameTable New feature - Added line information to JsonSerializationException New feature - Added JObject.Property overload with a StringComparison New feature - Added JsonMergeSettings.PropertyNameComparison New feature - Added support for multiple Date constructors with JavaScriptDateTimeConverter New feature - Added support for strict equals and strict not equals in JSON Path queries New feature - Added EncodeSpecialCharacters setting to XmlNodeConverter New feature - Added trace message for serializing to non-writable properties New feature - Added support for NamingStrategy to StringEnumConverter New feature - Added JsonLoadSettings.DuplicatePropertyNameHandling setting Change - JTokenReader now uses JsonReader.DateTimeZoneHandling setting for date values Change - Excluded TargetSite when serializing Exceptions without SerializableAttribute Change - Changed StringEnumConverter.ctor(bool camelCaseText) to obsolete Change - Changed StringEnumConverter.CamelCaseText to obsolete Fix - Fixed incorrect overflow when reading decimal values from JSON Fix - Fixed error message when trying to deserialize an abstract serializable type Fix - Fixed parsing decimals from a string with an exponent Fix - Fixed losing DateTime.Kind when deserializing ISO date strings Fix - Fixed calling constructors with ref and in parameters Fix - Fixed rare race condition in name table when serializing Fix - Fixed unhelpful exception message when unable to convert JSON value to DateTime Fix - Fixed error when deserializing empty array in DataTable Fix - Fixed deserializing empty string to empty byte array Fix - Fixed blank extension data values with required properties and deserializing with constructor Fix - Fixed ignored values being set in extension data when deserializing Fix - Fixed comparing equal integer and floating point values in JSON Path Fix - Fixed BsonReader when reading multiple content Fix - Fixed setting extension data with existing key Fix - Fixed including array attribute in XML with namespaces when converting JSON to XML Fix - Fixed error when serializing ref struct properties by excluding them from serialization Links Json.NET GitHub Project Json.NET 12.0 Release 1 Download - Json.NET source code and assemblies Tweet Feb 22 2018 Json.NET 11.0 Release 1 - .NET Standard 2.0, JsonConverters, JSON Path and more .NET Standard 2.0 The big new feature in Json.NET 11 Release 1 is targeted support for .NET Standard 2.0. There are two main benefits of a library like Json.NET targeting .NET Standard 2.0. The first is more APIs: Json.NET with .NET Standard 2.0 almost matches Json.NET on the traditional Windows .NET Framework in features. For example, fans of serializing DataSets to and from JSON rejoice, .NET Core now supports your pro-DataSet lifestyle: DataTable dt = new DataTable (); dt.Columns.Add( "PackageId" , typeof ( string )); dt.Columns.Add( "Version" , typeof ( string )); dt.Columns.Add( "ReleaseDate" , typeof ( DateTime )); dt.Rows.Add( "Newtonsoft.Json" , "11.0.1" , new DateTime (2018, 2, 17)); dt.Rows.Add( "NUnit" , "3.9.0" , new DateTime (2017, 11, 10)); string json = JsonConvert .SerializeObject(dt, Formatting .Indented); Console .WriteLine(json); // [ // { // "PackageId": "Newtonsoft.Json", // "Version": "11.0.1", // "ReleaseDate": "2018-02-17T00:00:00" // }, // { // "PackageId": "Newtonsoft.Json", // "Version": "10.0.3", // "ReleaseDate": "2017-06-18T00:00:00" // } // ] The other benefit of .NET Standard 2.0 is developers are no longer spammed with NuGet dependencies. UWP app authors for example saw NuGet pull in over 100 packages when referencing Json.NET. UWP supporting .NET Standard 2.0 and consuming a netstandard2.0 package eliminates that problem. JsonConverter Stuff Json.NET 11 adds a generic JsonConverterT. If you only care about serializing one specific type then JsonConverterT eliminates boiler plate code from your converter and keeps everything strongly typed. Also new is a UnixDateTimeConverter. There is no standard for serializing dates in JSON and so UnixDateTimeConverter is a useful converter for anyone who want to store time as an integer Unix epoch in their JSON. JSON Path Stuff Json.NET 11 adds support for the regular expression operator in JSON Path queries. JSON Path has no formal specification (other than a blog post ) but one common addition to...