CoreWcf.WebHttp should support System.ServiceModel.Web.Attributes
See original GitHub issueIf CoreWcf is compiled against netstandard2.0 AND framework, it would be possible to have CoreWcf support DotNet Framework System.ServiceModel.Web.Attributes
.
This would allow for a much more painless transition from dotnet framework to dotnet core.
Developers can run WcfCore on dotnet framework without changing the contracts, allowing for a smoother migration experience.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
What to use instead of System.ServiceModel.Web.WebGet ...
The CoreWCF Project team has released CoreWCF, a port of WCF to the .NET Core platform. It provides a compatible implementation of SOAP, ......
Read more >Upgrade WCF Server-side Project to use CoreWCF on . ...
Use the .NET Upgrade Assistant to upgrade an existing WCF Server-side project on .NET Framework to use CoreWCF services on .NET 6.
Read more >Using CoreWCF to Move WCF Services to .NET Core
The only difference is that the attributes are now from the CoreWCF namespace rather than System.ServiceModel namespaces.
Read more >Modernizing a WCF service to CoreWCF: Lessons learned
In this blog post, we will share the challenges faced and lessons learned from modernizing a Windows Communication Framework (WCF) service ...
Read more >CoreWCF v1.3.0 #946
We now support attributing your service implementation with the ASP.NET Core [Authorize] attribute. We support specifying the Policy, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mconnew Sorry, had just woken up.
I can try put together a PR after work today.
Sorry, I have been crazy busy recently. I did look at your PR briefly and there was at least one issue. One problem was checking the assembly name as that is going to be fragile. In the not too distant future we’re going to bring WebHttp support to the client side, and when that happens, the attributes will be in a totally differently named assembly. I’ll try and take a look later next week. I have another busy week coming up. Feel free to ping again around Thursday next week if you haven’t heard anything.