-
Notifications
You must be signed in to change notification settings - Fork 306
Feature Roadmap Vote #234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Transport – NamedPipe |
Transport – Msmq |
Transport - UDP |
CompletedWeb Standard – MTOM |
Web Standard – WS-Coordination/WS-AtomicTransaction |
Web Standard – WS-ReliableMessaging |
CompletedWeb Standard – WSDL |
Web Standard – WS-Trust |
CompletedWeb Standard – WS-Federation |
Web Standard – WS-Discovery |
WCF Feature - Routing Services |
Transport - gRPC The scope of this has expanded a bit. First we will desoapify the CoreWCF api's in a way which will make it easier to plug in other protocols such as Apache Avro, Orleans, JSON Rpc etc. The second step is providing an implementation which uses the desoapified api's to support gRPC/protobuf. We should also be clear, gRPC doesn't require protobuf, it's just the default data format (and should be supported as part of this feature). |
SecurityMode.Message - SOAP Protocol
|
Fixed - will be in 0.3.0 releaseDuplex contracts - Channel Shape |
This comment has been minimized.
This comment has been minimized.
CompletedWebHttpBinding support |
net.tcp port sharing support? I read #356 which is related, and there was a comment at the end that implied that there is something in the pipeline... [mconnew] This requires .NET 6. The ASP.NET Core team have added a feature to enable providing the socket yourself instead of it handling the socket listener. This is a prerequisite as is named pipes client support (coming later this year). So it's coming. |
WsHttpBinding - Message Level Security: SecurityMode.Message |
WSDualHttpBinding |
WS2007HttpBinding As in https://docs.microsoft.com/en-us/dotnet/api/system.servicemodel.ws2007httpbinding.-ctor?view=dotnet-plat-ext-6.0. We have a library that is currently .NET Framework 4.5. We are migrating to .NET Standard 2.0. |
ServiceHealthBehavior |
Multiple site bindings. |
Since .NET 7 support now distributed transactions, Transaction Flow, TransactionScope & ReliableSession its a must |
Azure Relay Support |
Support /js for WebHttpBinding |
hi, is Transaction Propagation supported? thanks, |
Will transaction control be added to the behavior of the service? For example: ReleaseServiceInstanceOnTransactionComplete and TransactionIsolationLevel in ServiceBehaviorAttribute |
What about following classes:
Does CoreWCF have any analogs? |
.net 8 support commitment |
Mutual TLS |
Any update when support of this is planned? This is most blocking part with our migration from .Net 4.6 to .Net 7 |
Is there any updates for net.tcp port sharing and net.tcp port activation for services deployed in IIS? |
How do I migrate from .NET Framework 4.8 without this class?: "BehaviorExtensionElement is for configuring the client using AppConfig which is not supported in Core." -- @StephenBonikowsky |
Blazor wasm support (at least equivalent to the old Silverlight 5 limits). Code level configuration, including the use of |
Each potential feature for porting/implementing will have a comment of it's own. To vote for a feature, add a 👍 reaction to the appropriate comment. Please don't 👎 anything, this isn't the appropriate place to express negative opinions.
If you wish to have a discussion about a feature in this issue, open a separate issue for the discussion and I'll will add a link in the feature comment to the discussion issue so others can easily find it. Any non-feature request comments will probably be deleted. What constitutes a feature in it's own right can be subjective and the initial list isn't intended to be exhaustive so if something important to you is missing, add a short comment with your feature request.
The text was updated successfully, but these errors were encountered: