Darren Rose

Yes that would make sense and certainly help new users understand when an error is not really an error so to speak. It is hard to know how to describe...

> Yea, linking to this thread is easy enough to do, with a concise summary of what it prevents raising as well. > > Let's get @tjscience opinion on that...

Excellent – thanks for letting me know – I will await progress whenever you get time Darren Rose PC Assist @ Home 01508 471459 [email protected] www.pcassistonline.co.uk From: Erik Berthold Sent:...

As per email from Blake this can be fixed client end by updating you Application Manifest File - just tested it and works perfectly https://www.prugg.at/2019/09/09/properly-detect-windows-version-in-c-net-even-windows-10/

RuntimeInformation.OSDescription gives the correct information, or at least the same information as changing the app.manifest does e.g. 10.0.19042.0 - if you want informaiton such as 1903, 2009, 20H2 etc then...

That is interesting to know, at least when I move to .NET 5 it will be okay. For now I am quite happy modifying the app.manifest to get my apps...

Yes as above quite happy to add manifest or if not I will use RuntimeInformation.OSDescription as suggested in previous post in a plugin to send correct information - thanks

any progress on this?

Excellent - thank you!

> What does that mean ?? I am assuming he meant Looks Good To Me, but whether that means just looking at the code, or actually testing it as requested...