7 ms·

First class. I would wager that most new .NET projects are primarily targetting Linux for deployment.

by kcb 4y ago

viraptor 4y ago
* for serverside
- kcb 4y ago
  Yea I'm guessing there's not a ton of fresh WPF or forms desktop apps being created. We've mostly moved to ASP.Net backends with React frontends wherever possible.
  - viraptor 4y ago
    Oh, there's definitely a huge amount of wpf and winforms created every day. That's what I meant. Those people just don't visit HN that often. (Then again, I created 4 windows specific wpf apps last year...)
- jameshart 4y ago
  Unity3D is probably one of the most widely used cross platform native app development platforms, and it’s taking c# .net code to Linux, macOS, android, iOS and browsers via wasm.
  - mythz 4y ago
    This doesn't speak to the cross-platform .NET Core runtime as Unity3D is built with C++ and still uses their modified fork of Mono to run C# code whilst their WASM uses their IL2CPP tool to convert .NET byte code to C++ before using Emscripten to convert to WASM.
    - mastax 4y ago
      Unity is moving to .NET 5+ and, if I remember their documentation correctly, the hold up is entirely on their side and not due to the .NET runtime not being cross platform enough.
    - HyperSane 4y ago
      So C# -> bytecode -> C++ -> Javascript? Wow.
capableweb 4y ago
Besides battling Visual Studio, `dotnet` cli and C# as a language, deploying a binary built on Windows to Linux was a breeze. If you're more used to the development environment, I bet it'd even be pleasant.
pjmlp 4y ago
Not really, plenty of VS tooling doesn't exist on VS4Mac nor VSCode. GUI frameworks don't consider Linux a deployment target, not even MAUI with its Xamarin heritage. Due to its Windows original focus, lots of libraries still rely on Win32, COM and other Windows specific issues. This also inhibits most big name CMSs, which still rely on .NET Framework, e.g. Sitecore, SharePoint, Dynamics,.... Targeting Linux containers is usually only done by us if writing greefield microservices without many dependencies outside the standard library.
- foepys 4y ago
  Stop wasting time with VSCode when doing professional development on .NET and use Rider on Linux and Mac. The C# addon for VSCode is lacking so many features compared to VS and Rider that it's mostly a toy. The Rider licensing cost is negligible when compared to a developer's compensation.
  - pjmlp 4y ago
    I don't waste time, we mostly target Windows with .NET, for UNIX workloads we usually use node and Java, as you can see by my last sentence there is very little .NET/UNIX for us, and even so, it is developed on Windows deployed on Linux. No need to pay for Rider licenses on top of the VS ones we already have.
- pleb_nz 4y ago
  Not quite true, people can choose to use other tools that do work well cross platform e.g. Rider. VS and VSC agent the only ponies in town. I don't even use VS on subdued installs anymore, it's no longer the better option.

First class. I would wager that most new .NET projects are primarily targetting Linux for deployment.

by kcb 4y ago

First class. I would wager that most new .NET projects are primarily targetting Linux for deployment.

viraptor 4y ago

* for serverside

kcb 4y ago
Yea I'm guessing there's not a ton of fresh WPF or forms desktop apps being created. We've mostly moved to ASP.Net backends with React frontends wherever possible.
- viraptor 4y ago
  Oh, there's definitely a huge amount of wpf and winforms created every day. That's what I meant. Those people just don't visit HN that often. (Then again, I created 4 windows specific wpf apps last year...)
jameshart 4y ago
Unity3D is probably one of the most widely used cross platform native app development platforms, and it’s taking c# .net code to Linux, macOS, android, iOS and browsers via wasm.
- mythz 4y ago
  This doesn't speak to the cross-platform .NET Core runtime as Unity3D is built with C++ and still uses their modified fork of Mono to run C# code whilst their WASM uses their IL2CPP tool to convert .NET byte code to C++ before using Emscripten to convert to WASM.
  - mastax 4y ago
    Unity is moving to .NET 5+ and, if I remember their documentation correctly, the hold up is entirely on their side and not due to the .NET runtime not being cross platform enough.
  - HyperSane 4y ago
    So C# -> bytecode -> C++ -> Javascript? Wow.

capableweb 4y ago

Besides battling Visual Studio, `dotnet` cli and C# as a language, deploying a binary built on Windows to Linux was a breeze. If you're more used to the development environment, I bet it'd even be pleasant.

pjmlp 4y ago

Not really, plenty of VS tooling doesn't exist on VS4Mac nor VSCode. GUI frameworks don't consider Linux a deployment target, not even MAUI with its Xamarin heritage. Due to its Windows original focus, lots of libraries still rely on Win32, COM and other Windows specific issues. This also inhibits most big name CMSs, which still rely on .NET Framework, e.g. Sitecore, SharePoint, Dynamics,.... Targeting Linux containers is usually only done by us if writing greefield microservices without many dependencies outside the standard library.

foepys 4y ago
Stop wasting time with VSCode when doing professional development on .NET and use Rider on Linux and Mac. The C# addon for VSCode is lacking so many features compared to VS and Rider that it's mostly a toy. The Rider licensing cost is negligible when compared to a developer's compensation.
- pjmlp 4y ago
  I don't waste time, we mostly target Windows with .NET, for UNIX workloads we usually use node and Java, as you can see by my last sentence there is very little .NET/UNIX for us, and even so, it is developed on Windows deployed on Linux. No need to pay for Rider licenses on top of the VS ones we already have.
pleb_nz 4y ago
Not quite true, people can choose to use other tools that do work well cross platform e.g. Rider. VS and VSC agent the only ponies in town. I don't even use VS on subdued installs anymore, it's no longer the better option.