Support ConfigurationManager based config for sharing with .NET Framework
See original GitHub issueI put together a POC a while back on incorporating ConfigurationManager to work for configuration of clients so that code could be shared between .NET Framework and Core easier. I’m opening this to see if there is interest. I put this together before CoreWCF was a thing and not sure if it would be an easy integration or not.
Here’s the link: https://github.com/twsouthwick/ServiceModel.Configuration
The API looks like this:
services.AddServiceModelClient()
.AddConfigurationManagerFile("wcf.config")
.AddDefaultChannel<IRoleService>("roles");
It uses ASP.NET Core IOptions and builds up the services so they can be directly injected. I only know the basics of WCF, though, so not sure how well this would extend to other use cases.
Feel free to close if there’s no interest in it. Much of the configuration code for this came from ReferenceSource and has been #if/#def
’d for types that didn’t exist when I was playing with it.
Issue Analytics
- State:
- Created 3 years ago
- Comments:21 (12 by maintainers)
Top GitHub Comments
@birojnayak, yes, I almost finished (there were some problems, so I didn’t make it by the end of April)
yes, this is exactly the solution when CoreWCF.ConfigurationManager is a separate project ( and respectively Nuget package) and it depends on CoreWCF.NetTcp, CoreWCF.Http @birojnayak, I really want to finish by the end of April.