Winforms: Build for System.Windows.Forms fails in Ubuntu

Created on 5 Jan 2020  路  6Comments  路  Source: dotnet/winforms

  • .NET Core Version: 3.1.100
  • Have you experienced this same bug with .NET Framework?: No (Didn't try, running on Ubuntu)

Problem description:
I run Ubuntu18.04.3 with .NET Core 3.1.100.
I use the release/3.1 branch
When I try to run dotnet build from the src/System.Windows.Forms/src directory, it fails with this message,

CSC : error CS1566: Error reading resource 'System.Windows.Forms.Arrow' -- 'Could not find file '/home/areller/playground/winforms/src/System.Windows.Forms/src/Resources/System/Windows/Forms/PropertyGrid/Arrow.ico'.' [/home/areller/playground/winforms/src/System.Windows.Forms/src/System.Windows.Forms.csproj]

image

Actual behavior: dotnet build fails (see above)
It seems that it can't find some resource (Arrow.ico), but this resource exists when I open it directly, and the build works on other systems (Windows and macOS).

Expected behavior: dotnet build should work
This is a screenshot of it working on macOS 10.14.6

image

I know that _winforms_ doesn't support Linux/macOS, but I want to experiment with it so I need it to build.

bug

All 6 comments

I think it breaks because of the casing, the file is in the lower case:
https://github.com/dotnet/winforms/tree/release/3.1/src/System.Windows.Forms/src/Resources/System/Windows/Forms/PropertyGrid

I'm not sure why it is working on the MacOS though...

@RussKie Right! I missed it
I see that there are a lot of other inconsistencies in the casing of resources. I'll fix them and update if the problem still occurs. Thank you.

As for why it works on macOS, I think that APFS is by default case-insensitive - https://support.apple.com/guide/disk-utility/file-system-formats-available-in-disk-utility-dsku19ed921c/18.0/mac/10.14

I'll fix them and update if the problem still occurs. Thank you.

馃憤
We accept PRs as well 馃槈

@RussKie The build works now, after I've fixed the resources files casing.
I'll publish a PR tomorrow.
Thank you for your help.

@RussKie / @areller is this issue ready to be closed then?

Yes, thank you for the heads up.

Was this page helpful?
0 / 5 - 0 ratings