IpcServiceFramework
.NET Core Inter-process communication framework (by jacqueskang)
wcf
This repo contains the client-oriented WCF libraries that enable applications built on .NET Core to communicate with WCF services. (by dotnet)
IpcServiceFramework | wcf | |
---|---|---|
1 | 9 | |
353 | 1,684 | |
- | 0.3% | |
10.0 | 9.0 | |
over 1 year ago | 3 days ago | |
C# | C# | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
IpcServiceFramework
Posts with mentions or reviews of IpcServiceFramework.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Question about Windows Form and Unity.
The accepted answer states the you could use named pipes, but at the time we could not create a reliable communication between unity and WPF, because named pipes would randomly drop with unity. We ended up using this https://github.com/jacqueskang/IpcServiceFramework with TCP. Both unity and the WPF app had a server and a client so we could do two-way communication. (Altough you can use a number of other solutions for this. Maybe create a file which holds messages, one process reads it and the other writes to it)
wcf
Posts with mentions or reviews of wcf.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-21.
-
Understanding the .NET ecosystem: The evolution of .NET into .NET 7
https://github.com/dotnet/wcf/issues/4887
-
Questions about OWIN and WCF from a high level.
Technically speaking WCF is quite a bit more than SOAP, I think this might be a good overview of what people used it for (or maybe use it even now).
-
Reentrant (Recursive) Async Lock is Impossible in C#
This article is wrong. It's hard to write and requires some out of the box thinking, but it's doable. You can see my implementation here. You can't easily implement cancellability though as you can't reset the state after an await as any changes you make will happen in a copy of the Execution Context. It could be done with a custom awaiter which chains a delegate to run before the await continuation so you can reset state on the callers ExecutionContext, but I didn't need that so didn't put the effort in.
-
CoreWCF v0.2.0 just released
MTOM on the client is now in code review in this Pull Request. After that's merged, I'll try to find time to port it to CoreWCF in the next month.
-
My little tool now supports both gRPC and REST testing
Next in my todo list is to add support for WCF, using CoreWCF. Long term, my goal is to also support GraphQL, SignalR, ODAta and WebSockets
-
Need help with submit supplier api call
There is another tool xscgen, that does not collapse container types and gets all the "inner types" correct but does not generate the Input/Output types or the client interface and client. dotnet-svcutil has another bug that prevents it from reusing external types.
-
https://np.reddit.com/r/workday/comments/o9o8q9/need_help_with_submit_supplier_api_call/h3d8oce/
There is a bug in dotnet-svcutil produces incorrect types and/or annotations when collapsing SOME pure container types into jagged arrays. dotnet-svcutil does not have the option to skip collapsing. During the contract implementation phase, which happens at runtime before the first request (ugh!), the code created viaRefEmit clashes with what the annotations specify and that exception is thrown.
-
CoreWCF releases first stable release
I thought that wcf client exists for core? https://github.com/dotnet/wcf
What are some alternatives?
When comparing IpcServiceFramework and wcf you can also consider the following projects:
CoreWCF - Main repository for the Core WCF project
Audit.NET - An extensible framework to audit executing operations in .NET and .NET Core.
Exceptionless - Exceptionless clients for the .NET platform
CoreWF - WF runtime ported to work on .NET 6
SoapCore - SOAP extension for ASP.NET Core
wd-soapgen - Meld xscgen and dotnet-svcutil tools to create corrected Workday SOAP client libraries
try-convert - Helping .NET developers port their projects to .NET Core!
csharp-language-server - Roslyn-based LSP language server for C#
omnisharp-vim - Vim omnicompletion (intellisense) and more for C#