Hi Lemmings, I wondered if anyone had successfully created a C# project that uses winforms on linux.
I just can’t figure out how to do it.
I use Arch and have full dotnet 6 and 8 packages; but I can’t dotnet new winforms as the template seems to not exist.
I also have installed mono and monodevelop installed, but even the simplest solution (Console App) can’t load correctly (currently I have /usr/share/dotnet/sdk/8.0.102/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.DefaultItems.Shared.targets(152,5) : error MSB4062: The "CheckForImplicitPackageReferenceOverrides" task could not be loaded from the assembly /usr/share/dotnet/sdk/8.0.102/Sdks/Microsoft.NET.Sdk/targets/../tools/net472/Microsoft.NET.Build.Tasks.dll. Invalid Image Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. but there were different similar errors before, these errors.
I don’t really want to boot up a VM every time I have to code on that project, but I’m starting to feel desperate about this.

TLDR: How does one create and work on a WinForms C# project with linux ? Any suggestions are welcome

Some clarifications for future readers :

  • It is for a school group project; winforms in imposed, which sadly won’t let me go with Avalonia
  • Dark Arc@social.packetloss.gg
    link
    fedilink
    English
    arrow-up
    7
    ·
    3 months ago

    This isn’t an answer to your question.

    I’m just curious, why winforms? Is there something that they do really well that you’re just dying to use on Linux? Trying to get a legacy application working? Familiarity?

    • nope@jlai.luOP
      link
      fedilink
      arrow-up
      2
      ·
      3 months ago

      none of that; it’s a school project which imposed winforms, else I’d have found some thing that would have worked for my linux

      • eveninghere@beehaw.org
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        3 months ago

        That syllabus likely assumes Windows. C# on non-Windows is not impossible, but it’s going to require effort infeasible for school projects like that one. As you’re facing it, C#'s packages were originally not meant to be used cross-platform, and god only knows the amount of problems that lie ahead. That clearly didn’t occur to the teacher’s head while they designed the course.

        • douglasg14b@programming.dev
          link
          fedilink
          arrow-up
          3
          ·
          3 months ago

          C# on non-Windows is not impossible, but it’s going to require effort infeasible for school projects like that one.

          You mean winforms (The windows specific UI) on non-Windows? Otherwise this is incredibly misleading, and plain wrong.

          C# in non windows is the norm, the default even, these days. I build, compile, and run, my C# applications in linux , and have been for the last 5+ years.

          • eveninghere@beehaw.org
            link
            fedilink
            arrow-up
            1
            arrow-down
            2
            ·
            edit-2
            3 months ago

            Not talking about winforms in that quoted part. I thought that was obvious.

            I don’t buy the second paragraph, especially as the phrasing is so loose it can mean anything.

            Edit: overall I think this will result in a typical internet conversation that turns into “lmao that’s the weakest argument I’ve ever seen!” “you’re so pathetic!” etc. etc.

            • Lucky@programming.dev
              link
              fedilink
              arrow-up
              3
              ·
              3 months ago

              Dotnet core (now just dotnet) was a full rebuild of the framework specifically for cross platform support so they could get more enterprise cloud hosting on azure, running everything on Linux

              Modern C# is built for first class Linux support for everything except UI

              • eveninghere@beehaw.org
                link
                fedilink
                arrow-up
                1
                arrow-down
                1
                ·
                edit-2
                3 months ago

                Nope. There are nuggets that lack ARM binaries, for example. And I’ve had enough troubles on macOS therefore.

  • fuzzzerd@programming.dev
    link
    fedilink
    arrow-up
    6
    ·
    3 months ago

    Check out Avalonia. It’s like cross platform WPF. Not winforms, but still pretty good and easy to start with.

  • thepiguy
    link
    fedilink
    arrow-up
    6
    ·
    3 months ago

    The closest I got was by just using avalonia. I had to use winforms for my uni and convincing my teachers to allow my team to use avalonia was not easy. Avalonia is not even remotely similar to winforms. You can try setting up a VM, but I understand that it is not a real solution. I found some docs for an old version of mono which referenced some of the winforms API, but I had no luck running it.

    • nope@jlai.luOP
      link
      fedilink
      arrow-up
      2
      ·
      3 months ago

      Well, I might try my luck with convincing my teachers to let us use avalonia but I’m not sure it will oucome to anything good. At this point I might as well use a VM for this, as I already had a VM for SolidWorks set up.

      • breadsmasher@lemmy.world
        link
        fedilink
        English
        arrow-up
        9
        ·
        3 months ago

        From the FAQ

        A small driver is required for each operating system supported. Currently we have drivers for: X Window System Win32 Window System macOS Window System

        so I think you’re right

      • cbarrick@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        3 months ago

        Of course Microsoft implemented it “for Windows”.

        The Mono project implements many of the .Net APIs in a portable way for other operating systems, including an implementation of WinForms on X11.

        OP specifically mentioned that they were using Mono.

  • JakenVeina@lemm.ee
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    3 months ago

    I know folks in the C# Discord have talked about getting WinForms to work on Linux, you could post a question there. But unless you’re specifically dealing with maintaining some legacy app, you should not be using WinForms, much less on Linux. Avalonia or Xamarin are definitely the way to go if you’re making something new and want cross-platform desktop support.

    Protip if you do go down that route: Tutorials tend to ignore the fact that you don’t have to use XAML to make anything in these frameworks. You should. But if it’s more comfortable for you to write WinForms-style imperative code that you’re used to, you 100% can, the APIs are not significantly different.

  • douglasg14b@programming.dev
    link
    fedilink
    arrow-up
    4
    ·
    3 months ago

    .Net 8 will work on Linux just fine. But winforms will not, it’s specifically a legacy windows-only UI framework.

    You’re going to have to jump through some incredible hoops to get it to work on Linux. Which are definitely not part of your normal curriculum.

  • Tramort@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    3 months ago

    I know it’s possible. I’ve used a keepass client on Linux that required Winforms; I think it was keepassx.

    Mono was how I got it to work.

    • nope@jlai.luOP
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      3 months ago

      well, mono in itself seems to work and I have successfully built the hello world winforms program using mono, but the monodevelop IDE won’t seem to work at all, which would make coding harder than it should be.
      I’ve also seen things online saying that monodevelop is half dead, so I don’t have much hope about this