What is the current appetite for a WCF data portal channel? #4850
b-higginbotham
started this conversation in
Ideas
Replies: 1 comment 3 replies
-
|
I think it fizzled due to lack of interest, and perhaps because CoreWCF was not mature back then. I'm thrilled with the idea of adding it to the codebase if you are willing to donate it. I need a contributor agreement and the code needs to follow csla standards and have the standard file header comment blocks. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I see there have been some discussions in the past that have fizzled without making any real progress. Here and here, for example.
I also have a need for a WCF data portal channel. So I built one.
The client side uses System.ServiceModel libraries that are a part of the .NET Framework and are also provided through packages in modern .net.
The server side uses System.ServiceModel libraries for hosting WCF in .NET Framework and CoreWCF packages for hosting in in asp.net core.
The channel is agnostic of target platform. In other words, a client built on modern .net can call a server built on .NET Framework, a client built on .NET Framework can call a server built on modern .net, etc.
If this is something that people are interested in, I can submit this data portal channel in a pull request to be added to the CSLA project.
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions