Merge pull request #134 from jacqueskang/history/v2.2.1

History/v2.2.1

Author: jacqueskang

README.md

@@ -4,16 +4,16 @@
 
 A .NET Core lightweight inter-process communication framework allowing invoking a service via named pipeline and/or TCP (in a similar way as WCF, which is currently unavailable for .NET Core). Secure communication over SSL is also supported.
 
-Support using primitive or complexe types in service contract.
+Support using primitive or complex types in service contract.
 
 Support multi-threading on server side with configurable number of threads (named pipeline endpoint only).
 
 [ASP.NET Core Dependency Injection framework](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection) friendly.
 
 ## Usage
  1. Create an interface as service contract and package it in an assembly to be shared between server and client.
- 2. Implement the service and host it in an console or web applciation
- 3. Invoke the service with framework provided proxy client
+ 2. Implement the service and host it in an console or web applciation.
+ 3. Invoke the service with framework provided proxy client.
 
 ## Downloads
 
@@ -160,4 +160,4 @@ Client certificates are not currently supported.
 
 If you want to process the binary data after serialisation or before deserialisation, for example to add a custom handshake when the connection begins, you can do so using a stream translator. Host and client classes allow you to pass a `Func<Stream, Stream>` stream translation callback in their constructors, which can be used to "wrap" a custom stream around the network stream. This is supported on TCP communications both with and without SSL enabled. See the `XorStream` class in the IpcServiceSample.ServiceContracts project for an example of a stream translator.
 
-Stream translators are also useful for logging packets for debugging. See the `LoggingStream` class in the IpcServiceSample.ServiceContracts project for an example of using a stream translator to log traffic.
+Stream translators are also useful for logging packets for debugging. See the `LoggingStream` class in the IpcServiceSample.ServiceContracts project for an example of using a stream translator to log traffic.

src/JKang.IpcServiceFramework.Core/Services/DefaultValueConverter.cs

@@ -8,6 +8,12 @@ public class DefaultValueConverter : IValueConverter
     {
         public bool TryConvert(object origValue, Type destType, out object destValue)
         {
+            if (origValue == null)
+            {
+                destValue = null;
+                return destType.IsClass || (Nullable.GetUnderlyingType(destType) != null);
+            }
+
             if (destType.IsAssignableFrom(origValue.GetType()))
             {
                 // copy value directly if it can be assigned to destType

src/JKang.IpcServiceFramework.Server/IIpcServiceBuilder.cs

@@ -14,5 +14,8 @@ IIpcServiceBuilder AddService<TInterface, TImplementation>()
         IIpcServiceBuilder AddService<TInterface, TImplementation>(Func<IServiceProvider, TImplementation> implementationFactory)
             where TInterface : class
             where TImplementation : class, TInterface;
+
+        IIpcServiceBuilder AddService<TInterface>(Func<IServiceProvider, TInterface> implementationFactory)
+            where TInterface : class;
     }
 }

src/JKang.IpcServiceFramework.Server/IpcServiceBuilder.cs

@@ -27,5 +27,12 @@ public IIpcServiceBuilder AddService<TInterface, TImplementation>(Func<IServiceP
             Services.AddScoped<TInterface, TImplementation>(implementationFactory);
             return this;
         }
+
+        public IIpcServiceBuilder AddService<TInterface>(Func<IServiceProvider, TInterface> implementationFactory)
+            where TInterface : class
+        {
+            Services.AddScoped(implementationFactory);
+            return this;
+        }
     }
 }