WinCopies.IPCService.Extensions 4.0.0

There is a newer version of this package available.
See the version list below for details.
dotnet add package WinCopies.IPCService.Extensions --version 4.0.0                
NuGet\Install-Package WinCopies.IPCService.Extensions -Version 4.0.0                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="WinCopies.IPCService.Extensions" Version="4.0.0" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add WinCopies.IPCService.Extensions --version 4.0.0                
#r "nuget: WinCopies.IPCService.Extensions, 4.0.0"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install WinCopies.IPCService.Extensions as a Cake Addin
#addin nuget:?package=WinCopies.IPCService.Extensions&version=4.0.0

// Install WinCopies.IPCService.Extensions as a Cake Tool
#tool nuget:?package=WinCopies.IPCService.Extensions&version=4.0.0                

IpcServiceFramework

A .NET Core 3.1 based lightweight framework for efficient inter-process communication. Named pipeline and TCP support out-of-the-box, extensible with other protocols.

Forked from https://github.com/jacqueskang/IpcServiceFramework

NuGet packages

Name Purpose Status
WinCopies.IPCService.Client.NamedPipe Client SDK to consume IPC service over Named pipe NuGet version
WinCopies.IPCService.Hosting.NamedPipe Server SDK to run Named pipe IPC service endpoint NuGet version

Usage

  1. Create an interface as service contract and package it in an assembly to be referenced by server and client applications, for example:

    public interface IInterProcessService
    {
        string ReverseString(string input);
    }
    
  2. Implement the service in server application, for example:

    class InterProcessService : IInterProcessService
    {
        public string ReverseString(string input)
        {
            char[] charArray = input.ToCharArray();
            Array.Reverse(charArray);
            return new string(charArray);
        }
    }
    
  3. Install the following NuGet packages in server application:

    > Install-Package Microsoft.Extensions.Hosting
    > Install-Package WinCopies.IPCService.Hosting.NamedPipe
    
  4. Register the service implementation and configure IPC endpoint(s):

    class Program
    {
        public static void Main(string[] args)
        {
            CreateHostBuilder(args).Build().Run();
        }
    
        public static IHostBuilder CreateHostBuilder(string[] args) =>
            Host.CreateDefaultBuilder(args)
                .ConfigureServices(services =>
                {
                    services.AddScoped<IInterProcessService, InterProcessService>();
                })
                .ConfigureIpcHost(builder =>
                {
                    // configure IPC endpoints
                    builder.AddNamedPipeEndpoint<IInterProcessService>(pipeName: "pipeinternal");
                })
                .ConfigureLogging(builder =>
                {
                    // optionally configure logging
                    builder.SetMinimumLevel(LogLevel.Information);
                });
    }
    
  5. Install the following NuGet package in client application:

    > Install-Package WinCopies.IPCService.Client.NamedPipe
    
  6. Invoke the server

    // register IPC clients
    ServiceProvider serviceProvider = new ServiceCollection()
        .AddNamedPipeIpcClient<IInterProcessService>("client1", pipeName: "pipeinternal")
        .BuildServiceProvider();
    
    // resolve IPC client factory
    IClientFactory<IInterProcessService> clientFactory = serviceProvider
        .GetRequiredService<IClientFactory<IInterProcessService>>();
    
    // create client
    IClient<IInterProcessService> client = clientFactory.CreateClient("client1");
    
    string output = await client.InvokeAsync(x => x.ReverseString(input));
    

FAQs

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on WinCopies.IPCService.Extensions:

Package Downloads
WinCopies.IPCService.Extensions.Windows

Package Description

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
5.1.0 635 8/27/2022
5.0.0 608 7/28/2022
4.4.0 603 8/27/2022
4.3.0 624 7/28/2022
4.2.0 444 11/4/2021
4.1.0 463 9/5/2021
4.0.0 347 7/9/2021

See Changelog