-
|
Is there a way to make a Windows XP compatible executable using Windows Forms? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
Can the same code for this Windows XP compatible executable also generate modern GTK and Mac executable with the same code/.NET version? |
Beta Was this translation helpful? Give feedback.
-
|
Eto.WinForms targets the following:
You can look this up here for .NET Framework, or here for .NET Core 6.0 As far as I know, Windows XP only supports up to .NET Framework 4.0, so there's no way for Eto apps to run on it. |
Beta Was this translation helpful? Give feedback.
-
|
Why is .NET Framework 4.6.1 needed as a minimum version for Eto? Can it be lowered to .NET Framework 4.0 so XP apps can be made too? |
Beta Was this translation helpful? Give feedback.
-
|
In theory, sure, both Eto.csproj and Eto.WinForms.csproj could add a net40 target. However, this would need some code changes to #ifdef out newer APIs not available in net40, and there are dependencies (Microsoft-WindowsAPICodePack-Shell) that would need to be figured out as well. I do not feel the complexity of maintaining a net40 target outweighs the need to support obsolete platforms, however. |
Beta Was this translation helpful? Give feedback.
-
|
It's a big, hard and thankless job to support frameworks that have been removed from support |
Beta Was this translation helpful? Give feedback.
In theory, sure, both Eto.csproj and Eto.WinForms.csproj could add a net40 target. However, this would need some code changes to #ifdef out newer APIs not available in net40, and there are dependencies (Microsoft-WindowsAPICodePack-Shell) that would need to be figured out as well.
I do not feel the complexity of maintaining a net40 target outweighs the need to support obsolete platforms, however.