print issue in WPF .net core 3.1 on Windows 8.1

[sandeep200321]

• .NET Core Version: 3.1
• Windows version: (winver) 8.1
• Does the bug reproduce also in WPF for .NET Framework 4.8?: No
• Is this bug related specifically to tooling in Visual Studio (e.g. XAML Designer, Code editing, etc...)? No If yes, please file the issue via the instructions here.

• Security issues and bugs should be reported privately, learn more via our responsible disclosure guidelines.

  Problem description: I created a sample WPF application in .NET Core 3.0 with below printed code. It just works fine in Windows 10 but not working in Windows 8.1. It is not giving any error either and hangs the application. Same code works in .NET Framework standard previous version without any issue even in Windows 8.1. Sample code:

Please advise how to fix it in windows 8.1 .Net Core 3.1.

Actual behavior: It is not giving any error either and hangs the application. Expected behavior: It should print the control and should not hang. Adding the error message in the attachment.

Minimal repro: Create a button and click on Print button. Click event code is below: private void Button_Click(object sender, RoutedEventArgs e) { PrintDialog printdialog = new PrintDialog(); printdialog.PrintVisual(this, "My first print job"); }

[sandeep200321]

Hi @RussKie @M-Lipin @Thea-Zhao please let me know if you can assist with this issue. I tried invoking show-dialog as well but after selection printer options, issue with freezehappens. It works fine in windows 10

[RussKie]

@sandeep200321 if this is a WPF issue, WPF team (@dotnet/wpf-developers) needs to look into it.

/cc: @LyalinDotCom @fabiant3

[sandeep200321]

Thanks @RussKie @LyalinDotCom @fabiant3 could you please help redirecting the issue to that group. Apreciate your help into this.

[sandeep200321]

Hi Team, Our release is impacted due to this issue so if you can assist on this issue would be great help. To give more context, We ported our old .net wpf application( .net framework 4.6) to .net core 3.1 and then found this freeze issue after porting. After analysis, we found that sample application above also has the same freeze issue. Apreciate if you can assist as it is impacting our release.

[vatsan-madhavan]

I’m moderately confident in this educated guess: This is possibly a regression (from netfx-> netcore) introduced by either https://github.com/dotnet/corefx/pull/36493 or https://github.com/dotnet/corefx/pull/38699 (or both; ie the general refactoring effort these PR’s represent).

More investigation would be needed to confirm this hypothesis, of course.

/cc @SamBent

[sandeep200321]

Thanks @vatsan-madhavan @SamBent Could you please let me know when it will be fixed.

[rufw91]

Im 3 weeks past deadline and just now i realized, i need not be stressed. Everything is under control. Somebody give me a beer.

[spacestr]

This is also causing an issue on our project using .NET 5.0 on Windows 8 / 8.1. We would really like to know when this issue will be solved as it is delaying one of our features from being released to customers.