Apologies. This hot weather tends to burn out the few braincells I have left these days. Sadly, all you can do is wait for a fix unless you can find one yourself. Skydiver is great at finding bug fixes and troubleshooting his way through unexpected problems and such. I'm not saying he will, but if you ask him nicely and are willing to wait until he has time, he may dig into the issue to see if their is a work around for you. He's helped me out in the past like this.
I misunderstood your post in brackets. I feel your pain. Imagine making 8 almost identical websites, only to realise you've been screwed by a number of horrible code bugs all of which are DNC related... Because It happened to me. The argument I was making above, is; Microsoft like to pre-release things when they are not ready, and then they allow their customers/developers to become their error loggers/code monkeys. That's why Microsoft have in place such a BS procedural request process ie. asking for more details to replicate the issue you are experiencing, rather than them fully testing their products before release which are the root cause of your issues. You become their logger, and maybe even their code monkey too.
The only way they will ever stop doing this; is for people to stop feeding them reports.
Frankly, I blame Bjarne Stroustrup, as he was the one insisting Microsoft follow their current path within the Framework back when he was writing his latest C++ version which has led to some of these issues we can see today. It's my opinion that Microsoft should have disbanded .net Frameworks long long ago. The only reason it's still alive today is because people are to stupid to use Linux and learn its ever-growing potential. And mainly because of the customer base Microsoft built up, which they didn't want to leave behind. Understandable I guess. But about 13 years ago they had a chance to improve the frameworks drastically, but their changes would have broken a lot of existing applications had they preceeded in that direction. Bjarne has admitted this himself, and it was a mistake in my opinion, and maybe his too.
I don't think .net frameworks has much of a future at its going rate. Mostly because many of the changes they have made is already breaking their own modern-day code. Having spent the last 20 years at this, It gets tiring being a code monkey running around reporting on forums and fixing their github mess. They should have worked longer on .net frameworks before going near DNC. Simple solution for me is to not use any of their products or frameworks. Evidently, its also easy to understand why they went opensource with .net.
Over the years participating on a number of forums like this one, it was easy to direct someone to the documentation and say read that, and you can't go wrong. Now I am finding myself testing documentation before I go telling people to go read it. Yes, the Microsoft documentation is not only out-dated in places, it also has misleading references, and resides today a lot of broken code examples. Something I hope they brush up on for their sake.
With programming languages like Kotlin coming along (which I also write along-side Python and others). Programming is moving in the right direction (away from Microsoft), but I just wish Kotlin wasn't based on Java class libraries. I've also made a dash for dabbling with Google API's, and I am ever-so leaning back on low-level programming once again. But one thing you will find as a developer, is that most of these frameworks are problamatic in one way or another and most are a waste of time, and like all frameworks, they die out... Php is a great example of this, with so many frameworks, and each have their own pros and cons. And most of them are dead today as php progresses. Admittedly .net is one of the longest living frameworks today.
All beit, we are not all bound to .net, we can choose to use OS X, Linux and others. I welcome the day a replacement comes along for all of them to merge. Wishful thinking, something we can only dream of.
Good luck with your project.
