CF.Serialization
.NET Compact Framework BinaryFormatter
CF.Remoting.Client & CF.Remoting.Server
.NET Compact Framework Remoting
  • Source & binary level compatible with the full .NET Framework
  • Lightning fast, ultra compact, low memory & CPU requirements
  • BinaryFormatter, Serialization Surrogates, Dataset, DataTable serialization and more...
  • Release (build 4.0.9.0105)
  • Source & binary level compatible with the full .NET Framework
  • Lightning fast, ultra compact, low memory & CPU requirements
  • Well-known, Singleton, TcpChannel with BinaryClientFormatterSink and BinaryServerFormatter Sink 
  • ChannelServices, LifetimeServices, Sinks, Proxy generators and more…
  • Secure & Compression Channel Sinks
  • Release (build 4.0.9.0105)
  • Want to see a robot powered by CF.Remoting? Go ahead!
v4.0 is here! CF.ASP.NET for .NETCF is coming soon
Build 4.0.09.0105 :: CF.Remoting
  • Fix: BinaryFormatter ignores return value of ISerializationSurrogate.SetObjectData().
  • Update: CallContext example was updated to demonstrate HttpClientChannel usage.
  • Fix: Occasional "MissingManifestResourceException" when SecureServerChannelSinkProvider is used.
  • Fix: DeflateStreamCompressionHandler and SharpZipLibCompressionHandler do not update the result stream position that may cause “EndOfStream” exception when both compression and secure channel sinks are used. Compression example was updated to demonstrate how secure channel sink can be added to the chain of the sink providers and establish secure connection with compression.
Build 4.0.08.0724 :: CF.Remoting, CF.Serialization {Release}
  • Added support for .NETCF v3.5 with Visual Studio 2008.
  • Added HttpClientChannel - implements a client channel for remote calls that uses the HTTP/HTTPS protocol to transmit messages.
  • Added Asymmetric Encryption Channel Sink - supports both .NETCF and the full .NET framework with dynamic encryption key generation and secure key exchange.
  • Compression Channel Sink - supports both .NETCF and the full .NET framework with built in DeflateStreamCompressionHandler and SharpZipLibCompressionHandler (source code included).
  • Substantial performance improvements.
  • Get to see the Microsoft Fiddler indicating compact device agent running CF.Remoting with HttpClientChannel:
Build 3.5.08.0122 :: CF.Remoting, CF.Serialization
  • Added support for hosting service objects with overloaded methods.
  • Fix: attempt to access well-known service types hosted on the device fails in certain cases when the type's assembly is signed. The bug was caused by inconsistent behavior of the System.Type on the full and compact frameworks as outlined here
  • Fix: serialization of the method response produces wrong byte stream when the call result contains more than one ref and/or out arguments. The generated byte stream could not be handled by the full .net framework side, resulting in ArrayOutOfboundException in RealProxy.PropagateOutParameters method.
  • Fix: rpgen produces improper code for the methods containing ref or out arguments.
  • Fix: deserialization of the DataSets may fail when dataset has nested DataRelation(s).
  • Fix: registration of the base types of published well-known service object(s).
  • Fix: deserialization of an object graph with the members of nullable type(s) may fail.
  • Fix: serialization of an object graph with the multidimensional array(s) may fail in certain cases.
  • CF.Remoting performance improvements.
  • Documentation fixes.
Build 3.4.07.1025 :: CF.Remoting, CF.Serialization
  • CF.Remoting.Server product release: Well-known services, TcpServerChannel that uses BinaryFormatter, LifetimeServices and much more.
  • CF.Serialization performance improvements.
Build 3.3.07.1010 (3.3.10.10) :: CF.Remoting, CF.Serialization
  • The Beta of the CF.Remoting.Server product: Well-known services, TcpServerChannel that uses BinaryFormatter, LifetimeServices and much more. 
  • Attached is a snapshot of the Remote Registry Editor (RegEdit) console implemented via the full .NET remoting and connected to the PocketPC (Symbol MC50) running remoting registry server implemented via CF.Remoting.Server component(s). You can find the source code of this project in Remoting\Examples\CS\RegEdit directory.
  • CF.Remoting.Client Visual Basic rpgen support, examples.
  • Fix: In rare cases the DataTableSerializationSurrogate fails to deserialize empty DataTable.
  • Other minor bug fixes and improvements.
Build 3.1.07.0921 (3.1.9.21) :: CF.Remoting, CF.Serialization
  • Substantial rpgen tool improvements: code generation for indexers, warnings for unsupported events and return types inherited from MarshalByRef. The tool has been refactored to support the code generation for sophisticated class hierarchies.
  • Minor bug fixes.
Build 3.0.07.0919 (3.0.9.19) :: CF.Serialization
  • Added Hashtable serialization/deserialization example demonstrating the usage of built-in Serialization surrogates as well as showing how the types with missing default constructors can be deserialized via handling of the FormatterServices.ResolveObjectConstruction event.
  • In rare cases the full .NET framework BinaryFormatter fails to deserialize the byte stream produced by CF.Serialization when it contains both remoting headers and graph contents. Serialization procedures were modified to keep MS BinaryFormatter happy with the bits.
  • Attempt to add the serialization surrogate into the SurrogateSelector that has already been registered raises an Exception with the message: “Value does not fall within the expected range.” instead of raising ArgumentException: “A surrogate already exists for this type and context.”.
  • Serialization examples have been adjusted to eliminate nonsense Visual Studio security warnings when sample solution is opened.
  • Our product installers are signed with Authenticode Signature and time stamped, so you, End User, can confirm that software really comes from the publisher who signed it (us), you can verify that our software has not been altered or corrupted since it was signed and code will be as safe and trustworthy to you as it would be if we shrink-wrapped it and sold it off a store shelf.