Today we are announcing the retirement of the Visual Studio for Mac IDE. Visual Studio for Mac 17.6 will continue to be supported for another 12 months, until August 31st, 2024, with servicing updates for security issues and updated platforms from Apple.
  • wth@sh.itjust.works
    30·
    1 year ago

    Well… this is pretty crappy.

    I built a Xamarin app (mac/iOS) because I wanted portability to windows. Then I was forced to upgrade to .net 6/7 because of a library I needed, and that meant upgrading to .Net for Mac/.Net for iOS (which is part of MAUI, but not using MAUI UI controls). MAUI is definitely undercooked at the moment.

    What an awful and painful process, but I’m finally there… and they drop the main IDE for development. Damn.

    VSCode doesn’t have a visual UI designer (well… neither does VSMac, but it does prepare a copy of your project and opens XCode for editing the storyboard/images, and copies changes back). So does this mean they will add that to VSCode? Or will we all have to switch to raw edits of XML to create UIs like you have to do with MAUI? Ick.

    Developing GUIs for windows using MS tools is a lesson in frustration, especially when you want to have cross platform capabilities… WPF -> WinForms -> Xamarin -> Xamarin.Forms -> MAUI/.Net for {Mac,iOS}… Not to mention UWP… Each transition is a rewrite. Damn.

    • abhibeckert@lemmy.world
      4·
      1 year ago

      What an awful and painful process

      Yeah… that’s why almost nobody uses Xamarin. The fast approaching train if you’re invested in Xamarin (for others, the light at the end of the tunnel) is SwiftUI which is the first good SDK designed to create cross platform user interfaces.

      SwiftUI isn’t on Windows yet - but it’s coming.

      • wth@sh.itjust.works
        8·
        1 year ago

        Its hard to make a commercial decision for something that’s coming someday. But I hope it does arrive - I like Swift as a language (OMG - it was such a pleasure after the ugliness that is Objective C).

    • realharo@lemm.ee
      3·
      1 year ago

      This may not be a popular opinion, but if the app is large enough, just use Electron.

      • wth@sh.itjust.works
        2·
        1 year ago

        I really like the idea of having a web UI for its portability and richness (esp thanks to CSS being so close to consistent across all platforms). But I have a metric tonne of business logic and ZKE code in C#/.Net running on Mac/iOS. From your prompt, I did just find Electron.Net, so perhaps there is hope.

        And, AFAICT, electron can’t be used for iOS apps on the App Store (am I still wrong about that??)

        Plus (personal bent) I did a ton of JavaScript years ago when truthiness and indeterminate behaviour was rampant back in ES5 days. I’m a purist and found it a little ugly, but incredibly fast. Then I found dart which compiled to JS, and I decided that JS made a better assembly language than a usable language. Sadly dart has remained a minor player. JS has moved on and I see lots of the old ugliness (like iterating through properties, exceptions and a sync) has gone away. ES13 looks pretty good, although I haven’t played with it yet.

        • VeryNiiiice@sh.itjust.works
          41·
          1 year ago

          Have you looked into Flutter? It uses Dart and can compile to native apps for android, ios, windows, Mac, Linux, and web.

          • wth@sh.itjust.works
            1·
            1 year ago

            After I saw your note, I had a quick catchup on that project.

            It looks awesome, with the promise of mobile and desktop, and the ability to make apps that can be uploaded to the AppStore. Plus its Dart which is a pretty well structured language. Its ticking a lot of boxes…

            Then I ran « wc -l » on my support libraries (i.e. not UI code) - 64k LoC that would need to be rewritten in dart. But then I noticed Flutnet. its probably an abomination linking the two… but it could be promising.

            Thanks for the pointer.

    • loics2@lemm.ee
      20·
      1 year ago

      Well at this point, don’t trust any framework Microsoft pushes. They told everyone UWP was the future for Windows after WPF, then stopped for WinUI and the app SDK…

      • gk99@beehaw.org
        6·
        1 year ago

        The problem with UWP is that nobody liked or wanted it, so obviously it died. Developers got locked into a walled garden, Xbox users saw no benefit (until recently with emulators, but I digress), Windows phone users practically didn’t exist to build apps for, and PC gamers got the real short end of the stick with everything becoming a buggy, locked-down, performance-hampering, feature-lacking mess.

        Outside of letting Microsoft half-ass port some Xbox titles to PC, it was pretty much useless.

    • Spyros@programming.devOP
      4·
      1 year ago

      I have started using Avalonia, and even though I am still learning, I am very satisfied with it. There are growing pains obviously, but as you said, I have no confidence in Microsoft UI frameworks.

    • wth@sh.itjust.works
      1·
      1 year ago

      MAUI’s pretty undercooked at the moment. Editing UIs in raw XML, incomplete control set, bugs.

      One day could be useful, and there are some 3rd parties providing controls… but of course this is microsoft so they will work on it for 2-3 years, and then write something new, throwing MAUI into the dustbin.

  • charlybones@programming.dev
    25·
    1 year ago

    In my previous company I used VS for Mac, it wasn’t a great experience… but it was better than nothing. Then along came a Rider license…

    The tooling for VS Code might have improved, but Rider is the IDE of choice… even on windows.

  • mintiefresh@lemmy.ca
    9·
    1 year ago

    Darn. I was really hoping it would improve.

    I guess I can just use VS Code for now. And maybe use Rider in the future.

    • wth@sh.itjust.works
      3·
      1 year ago

      Rider doesn’t support MAUI. Nor does it support .net for iOS and .net for Mac which are part of MAUI and the natural upgrade from Xamarin. I downloaded Rider a few months ago and enjoyed being able to switch between VSMac and Rider, and especially enjoyed using CoPilot in Rider.

      However Rider has a couple of nasty bugs that have been there for years - one of which was to ignore breakpoints. That came and went on me for a while.

      • wth@sh.itjust.works
        1·
        1 year ago

        I take back this comment partially. As 2023.1 (which I have), rider failed to support MAUI. As at 2023.2, they say they have preview support available. I’ve downloaded, and am giving it a try.

      • BaskinRobbins@sh.itjust.works
        1·
        1 year ago

        I’ve never experienced the breakpoint issue with Rider but I do find myself needing to invalidate cache and reload every now and then if I’m using it heavily. To be fair though I’ve had to do the same with VS for windows. It was always nice to use VS for Mac as a last resort sanity check though just to roll out that Rider is having issues and not my code.

        • wth@sh.itjust.works
          1·
          1 year ago

          Cache clearing has been mentioned as a way to fix issues, but it didn’t work for me. I agree with your comment about the value in having a second IDE though.

  • revs@feddit.uk
    7·
    1 year ago

    Not surprised after the the main VS Mac developer left MS a few months ago.

    • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.one
      4·
      1 year ago

      I’m not surprised lol.

      At my workplace I occasionally do work on an AutoCAD lisp add-in, half the time I don’t know what I’m doing when something isn’t quite working right 😭

      My manager is tempted to drop support because none of us really know what we’re doing with it… the original dev is long gone and none of us know LISP

    • abhibeckert@lemmy.world
      1·
      1 year ago

      You can run an insider preview version of Windows on Apple Silicon Macs (can’t boot yet, but you can run it in a VM).