I'm trying to move to Core, but I'm running into a lot of problems that seem common. Since things (like names) have changed some much some of the answers I find no longer work. I'm looking for an example or good start to do the following.
I have an MVC application that uses a SOAP service. When I move to Core I can no longer use it directly. I create a new WCF project to wrap it, and with the https://blogs.msdn.microsoft.com/webdev/2016/06/26/wcf-connected-service-for-net-core-1-0-0-and-asp-net-core-1-0-0-is-now-available/
project I can now use it as a connected service. The problem is now that my types must be declared in two places. The service can't be the "master" so I can't declare them all as data contracts. So I think I will create a library to hold all of the types. But what kind and for what target? My WCF project wants a DLL and my MVC want Nuget. I tried many different approaches but none were working. I tried to create a library I could share, but I've tried several types (e.g., portable) with no luck. I thought I was getting close to an integration solution by creating wrappers and then Nuget for them, but I would end up getting errors about things being defined in assemblies that weren't referenced. This may sound confusing (it is), but if you've been here you know what I'm talking about. Solutions I've seen talk about which version the projects must target and adding dependencies in my json, but everything in the examples is outdated. I've been fighting this for days now.
My questions is, is there a CURRENT example out there that explains how to integrate WCF/SOAP, Class Library, and MVC projects in Core, that explains what project types, target frameworks, versions, etc. of everything you need to get these things to work together?