The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
God only knows what ASP.NET vs. ASP.NET Core conversion would be like though.
I recently had to use .NET Framework for a WCF service.
I used to be quite a fan of EF, but for the past couple of years I've only been using EF Core.
Tried to run EF, but it was a PITA to go back, so I tried EF Core and it runs very nicely with my WCF Service.
Then I had to share the package between the WCF Service and an Azure Function (in .NET Core), so I switched the project type to a .NET Standard 2.0 project and everything just worked
The only downside I found was that I now needed an extra console app for running the EF Core Migrations tooling, for some reason that didn't work with the Azure Function project.
All these .NET versions are quite confusing though... And it seems there's another one coming to rule them all...[^]