SaaS 2022.1 >> 2022.2 - the much awaited upgrade

Santiago I did notice issues with having .NET Core Runtime on my PC. Even Epicor aside, for example I use LINQPad and suddenly I got
The type initializer for 'Epicor.Data.EpiDataContext' threw an exception. because Serilog could not be found in Epicor.Hosting.dll (Inner Stack).

I removed .NET 6 Runtime from my PC and long and behold, all is back to normal.

I think .NET 6 should supplement .NET 4.7 but what happens it actually breaks stuff when compiling code on the PC arghhhhh! Its not an Epicor issue, just a .NET Backwards compatibility issue.

Even tho I had NuGet specific packages for EntityFramework, somehow .NET 6 Runtime messed it up.

Now I can explain this too :slight_smile:

Basically - Remove .NET 6 Runtime from your Client PC and all your BPMs and issues will be resolved and you wont have to include some special assembly in your BPMs.

2 Likes