Skip to main content
H.ProxyFactory.Pipes package icon

H.ProxyFactory.Pipes

Features: - Create proxy objects that look exactly like the original objects - Proxy target can be located anywhere where there is access to pipes โญ Last 10 features: - feat: Added RemoteProxyServer.ObjectCreated event. 2021-11-28 - feat: Implemented safe CreateObjectAsync. 2021-10-30 - feat: Added try catch to example app. 2021-10-30 - feat: Added CLSCompliant(true). 2021-10-30 - feat: to auto-releases. 2021-10-29 - feat: Implemented example WPF app. 2021-10-29 - feat: Added empty wpf app. 2021-10-29 - feat: To file-scope namespaces. 2021-10-29 - feat: To net6.0 and C# 10. 2021-10-29 ๐Ÿž Last 10 bug fixes: - fix: Changed CI build to windows-latest. 2021-10-30 - fix: Added Factory.LoadAssemblyAsync to example app. 2021-10-30 - fix: Fixed H.ProxyFactory.Pipes warnings. 2021-10-30 - fix: Fixed H.ProxyFactory warnings. 2021-10-30

Total Downloads
22.4K
22,383
Published
Nov 27, 2021
Latest stable version

Install

.NET CLI
dotnet add package H.ProxyFactory.Pipes --version 0.8.4
Package Manager Console
Install-Package H.ProxyFactory.Pipes -Version 0.8.4
PackageReference
<PackageReference Include="H.ProxyFactory.Pipes" Version="0.8.4" />

Frameworks

.NETFramework4.6.1 .NETStandard2.0 .NETStandard2.1

Dependencies

H.ProxyFactory
.NETFramework4.6.1
[0.8.4, )
H.Pipes
.NETFramework4.6.1
[1.14.6, )
H.ProxyFactory
.NETStandard2.0
[0.8.4, )
H.Pipes
.NETStandard2.0
[1.14.6, )
H.ProxyFactory
.NETStandard2.1
[0.8.4, )
H.Pipes
.NETStandard2.1
[1.14.6, )

Adoption guide

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

Compatibility metadata lists 3 target frameworks; confirm the exact target used by your application.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.