Two issues with Windows 10, version 1903

ctodx
25 July 2019

Although version 1903 of Windows 10 is still an optional upgrade, I’m going to guess that more people will be applying it as more news and information about it is revealed by Microsoft. Hence, in order to ensure that our code still works under this new upgrade, we have been doing some testing, the results of which means I have a couple of warnings to impart.

In essence, we have two separate issues with this latest Windows update, and both affect a wide range of our releases. (I will add that we are definitely in touch with Microsoft about these issues, and hopefully solutions will be forthcoming quickly.)

The first of these two issues is related to the new .NET Framework version 4.8, which is included with the update. In short, the bug prevents debugging a WinForms application under Visual Studio 2017 and 2019. Doing so will cause the app to crash with an unhandled exception:

The only way we’ve discovered to avoid the problem is to ensure the application is compiled to target 32bit, or to launch the app without using the debugger. This issue affects all of our WinForms releases.

The second issue is related to the Desktop Window Manager (DWM) and how we use the Windows Acrylic API to create a fluent design. This particular issue affects our demos, and also those customers who use our NavPane control with the Acrylic option enabled – that is, for v18.1 onwards. Unfortunately we have no workaround as yet. The hotfix we shall use for now is to basically disable the Acrylic feature if a specific Windows update is detected.

Again, we are in touch with Microsoft about these issues, but thought them important enough that we let you, our customers, know as well.

5 comment(s)
Jeff Stiegler
Jeff Stiegler
Thank you, thank you.  I very recently upgraded to 1903 (which took 5 hours) and have not experienced issue  number 1 because I am still using framework 4.7.2  Will not be changing to 4.8 until you guys give it two thumbs up.
25 July, 2019
Christopher Jay
Christopher Jay
So issue #1 only occurs if your application is built on Framework 4.8?  It's a little unclear.
25 July, 2019
Jerzy Rozmyslowicz
Jerzy Rozmyslowicz
I already use 4.8 and do not have any issues with Devexpress
25 July, 2019
Customer91416
Customer91416
Hummm I wonder if this is why I was having so much trouble getting SQL Express to load. 
26 July, 2019
Julian Bucknall (DevExpress)
Julian Bucknall (DevExpress)

All: A quick comment to provide some clarification.

Firstly, we do not have any further information about all this at the moment. Conversations with the relevant people are still under way.

Secondly, I was perhaps not ultra-clear about the crash we're seeing: it only happens when we use debug builds of our assemblies for testing, and, at that, only when debugging an app using the Visual Studio debugger. If you're just running an app with the normal assemblies, no problem that we know of.

Lastly, the Acrylic issue I mentioned is not a crash problem, it's a severe slowdown problem. Well OK, not quite a "Let's have fun watching the individual pixels being drawn" issue 😉 but the slowdown is noticeable...

Of course, as soon as we have further news or even a fix, we'll let you all know.

Cheers, Julian

 
1 August, 2019

Please login or register to post comments.