The intended audience for this blog post is one who wants to migrate from the full .Net Framework to .NET Core and has a large library of WCFs, now considered technical debt. This post will attempt to at least partially answer the question: How difficult will it be to migrate my current code base of WCFs to gRPC in .NET Core?
This post is provided by Senior App Dev Manager, Vishal Saroopchand who asks the question, “How do you decide what Communications Stack to use in your Service Fabric applications?”
How do you decide what Communication Stack (Remoting, WCF, Custom Implementation) to use in your Service Fabric applications?
The GZip encoder is not included in NetCF as it is on the desktop WCF, but it isn’t hard to build yourself and in fact we have released a sample of exactly how to add your own GZip encoder to NetCF:
So many people have asked me for it lately I thought I’d better just post the link.
The Windows Communication Foundation introduced the new DataContractSerializer to replace the XmlSerializer in many scenarios. The DataContractSerializer is faster than the XmlSerializer, but has certain limitations. For example it does not support serializing an object’s members as XML attributes. When you write a WCF client that calls a service,
The .NET Compact Framework 3.5 Power Toys have been released. You can download them from here.
Tools included in this package: Remote Performance Monitor and GC Heap Viewer – Provides real time counter data (ranging from Garbage Collector activity to type loading info) on a running NETCF application.
A bug was discovered recently in the .NET Compact Framework version 2.0 (SP2 and earlier) and 3.5 that causes HttpWebRequest’s directed at some HTTPS servers to fail with this error: (for web services)
System.Net.WebException: Unable to read data from the transport connection.
With the .NET Compact Framework 3.5 release which comes with Visual Studio 2008, a new Windows Communication Foundation transport is introduced that uses email as the communication mechanism.
Others have already blogged about this new transport including Roman Batoukov and David Kline.
The .NET Compact Framework 3.5 adds a subset of the Windows Communication Foundation (WCF or “Indigo”) to smart devices, allowing them to communicate with desktop WCF components with all the flexibility of multiple, interchangeable service bindings and endpoints. Although it ships out of the box only with support for message-level communication (no service calls,
The .NET Compact Framework team just released the Consumer Technology Preview (CTP) of the Power Toys for .NET Compact Framework 3.5. These Power Toys are tools to help you build, debug and optimizie your NetCF 3.5 applications.
My personal favorite is the NetCF ServiceModel Metadata Tool (NetCFSvcUtil.exe) which allows NetCF clients to call web services using the Compact WCF stack.
[Updated: 21Nov07 to clarify that custom headers are supported, but not in NetCFSvcUtil proxy generation] [Updated: 27Aug07 to correct Gzip sample, and clarify on transports & extensibility] [Updated: 23Aug07 to add SecurityAlgorithmSuite enumerable]
Many people have been asking about what subset of .NET 3.0’s Windows Communication Foundation (WCF) will be supported by the .NET Compact Framework 3.5.