lorenzck / windowsformsaero Goto Github PK

Can you please add .net core 3.1 support, I get this warning:

warning NU1701: Package 'Windows-Forms-Aero 3.1.1' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETCoreApp,Version=v3.1'. This package may not be fully compatible with your project.

I noticed that ContextMenu is not available for .net core 3.1 which is used in SplitButton and needs to be removed.

Hello,
First, I'd like to thank you for your library. I've been using it for some time with great success.

Recently I changed all of my WinForms applications to 64-bit versions.
After that TaskDialogs stopped working.
Showing of a simple dialog still works, but you can't change any of the properties of a dialog that is already shown. Application is failing with System.OverflowException.

I tracked the problem to windows message loop procedure and message class itself.
Currently Message class has WParam and LParam properties defined as int (32bit) and that is causing problems.

Setting a new property value actually sends new windows message, so for example:
There is a Message class constructor that takes string as a parameter.
It uses Marshal runtime to get a pointer (IntPtr) to character data and it tries to assing that value to LParam - which is 32bit int. That results in an overflow exception.

It seems that the problem is easily solved by changing type of WParam and LParam properties to IntPtr - a type whose size is platform dependent, just like the underlying WPARAM and LPARAM types from WinAPI.

Please take a look at the following changes that I made:
https://github.com/pziezio/WindowsFormsAero/commit/0a4cef194d40760f58e10427e1bb8b41c5b0d854#diff-3d7d9b2fdd0df5be3ed6890538248201

I could submit a pull request for this change, but I don't have any experience with creating configuration for multi-platform NuGet packages and I don't know how a new package configuration should look.

Best regards
Piotr Zięzio

Are you planning on supporting the new transparency options introduced in Windows 10, 1803?

TaskDialog calls should be redirected to a custom class that mimics the behavior and appearance of Vista’s Task Dialogs for previous Windows versions (and/or other OSs).

Expected behavior

Press F11 to step into code and debug the code

Actual behavior

because no source info are found in the provided PDB, debugger steps over

Solution:

enable Source Link to fetch the source from github during debugging to be able to step into the code.

Aero Wizard.

It would be nice to have an easy way to access the new Vista common dialogs.
Ookii.org has a very nice implementation that automatically chooses a compatible version of the dialog to show (even on non-Vista systems).