191–200 of 231 posts
They should fix github issues and write in-depth tutorials, instead of AI features or minimal API.
https://github.com/CarterCommunity/Carter
My current absolute favorite is .NET Aspire. Build distributed applications with an OTEL support dashboard - up and running in minutes.
https://learn.microsoft.com/en-gb/dotnet/aspire/whats-new/do...
Only gap in Aspire is deployment (k8s) tooling which is on the way.
Earlier quoted context omitted.
> .NET was the most sane programming ecosystem that I worked in. Having written libraries in .Net I fully disagree with that notion. First insanity is figuring out what in the fuck you need to support. .Net framework or .Net standard or .Net Core or Mono (or .Net Duplo or .Net dot nes :P). Second is the Source generators. I swear using t4 templates is the saner option. I've had cached artifacts appearing out of the f…
> First insanity is figuring out what in the fuck you need to support. Since I no longer support .NET Framework, it's just .NET now. .NET was two platforms for a while and they did a lot of weird stuff to make that work (.NET standard) but it's been one platform for many versions now so that specific difficulty can mostly be ignored.
Earlier quoted context omitted.
Windows and Office never adopted .NET for client code in the first place except for the Longhorn period in the mid-00s, which burned them and put them off it. If that didn't stop .NET in the two decades between then and now, I'm not sure why it would today. Actually, Windows is just now starting to adopt C# now that AOT is supported (I think the new native Copilot app is C#).
Many Windows Server admin tools (such as Server Manager or Virtual Machine Connection) and MMC snap-ins (e.g. Event Viewer, Hyper-V Manager) are written in .NET Framework 4. PowerShell is .NET Framework 4. Everyone’s favorite bloated IDE (Visual Studio) is .NET Framework 4 as well. In the Office land, Excel’s Power Query is .NET Framework 4. Adopting the modern .NET is probably harder due to its lifecycle.
Earlier quoted context omitted.
You're clobbering together a bunch of different stuff and not making a ton of sense. C and C++ are very different languages, and that's especially true when doing interop with them from other languages. For C-based libraries, P/invoking is trivial in C# and has been around forever. And it's cross-platform, working identically on Linux and macOS. I have no idea how you can say ".Net hasn’t ever really had that kind of…
The only reason is name mangling. You can disable this or export declspec it and keep the C-like signature. Painstakingly recreate the API in C#, using P/Invoke, and hope for the best. It wasn’t until late 2015 that we got codegen to “automate” this, or roll your own. My perspective is from a first adopter, not an insider, 24 years ago, so I can’t speak to motive but as a customer, it felt exactly as I described. The…
Also during .NET 1.0 days, Microsoft had a Website where you could paste any well known Win32 API or related SDK, and it would spit the annotations.
What was never as good in .NET as it was in VB 6 and still is in Delphi and C++ Builder to this day, was creating and consuming COM, which is kind of annonying given how much Windows team loves it.
At least it isn't as bad as the multiple reboots in C++, which I will keep asserting that from all of those, MFC still has the best tooling to handle COM.
Earlier quoted context omitted.
Many Windows Server admin tools (such as Server Manager or Virtual Machine Connection) and MMC snap-ins (e.g. Event Viewer, Hyper-V Manager) are written in .NET Framework 4. PowerShell is .NET Framework 4. Everyone’s favorite bloated IDE (Visual Studio) is .NET Framework 4 as well. In the Office land, Excel’s Power Query is .NET Framework 4. Adopting the modern .NET is probably harder due to its lifecycle.
Calculator is C# as well (though apparently that's somewhat recent: https://github.com/microsoft/calculator/pull/1598 ).
.NET was the most sane programming ecosystem that I worked in. Great CLI, great package manager, very good stdlib, strong IDEs/Debuggers, etc. but sadly interesting jobs like OSes, databases and compilers are way less common than in C++ world :(
Do you know about any sizeable open source projects written in C#, other than what Microsoft has produced? I rarely come across anything written in it.
.NET was the most sane programming ecosystem that I worked in. Great CLI, great package manager, very good stdlib, strong IDEs/Debuggers, etc. but sadly interesting jobs like OSes, databases and compilers are way less common than in C++ world :(
I despise working with Nuget. Whether it's a restore, managing your csproj, or publishing packages, compared to NPM it's an absolute mess.
All these changes, yet still no satisfactory UI framework. Still no migration path from WinForms to something modern. I love .NET but if you're taking on an older desktop app that is still using VB.NET and WinForms it feels like Microsoft have decided to let you circle the drain with no supported way forward into MAUI or whatever stupid XAML UI they decided is the solution these days. On a server, .NET is fantastic a…
I've tried each iteration of UI paradigm they've tried since WinRT and never really had any significant problems with any of them. WinRT, UWP, WinUI, MAUI... But then they aren't even willing to invest the time to dogfood their own products and fully replace the windows UI. Really doesn't inspire confidence. I suspect they also made a bad bet by going so hard on blazor without putting more support behind WASM itself.…
As someone that was deeply invested into WinRT since Windows 8, and went back into distributed systems and Web after all the disappointment regarding how managemetn handled it.
Everyone on the Windows development ecosystem has had enough from the multiple reboots and tool changes, UWP never being as good as WPF, WinUI iterations even worse, the team now went radio silent, the last community call was a disaster,...
Earlier quoted context omitted.
I prefer VS Code... though MS has for better or worse kept the .Net tooling relatively weak. I'll use Rider or VS on a few occasions... then retreat back to Code as much as I can. For split web projects, definitely work on the web ui in VS Code.
I used to like VS Code, but something about it changed and it does not feel as snappy as it once did for me. Now I prefer Zed.
.NET was the most sane programming ecosystem that I worked in. Great CLI, great package manager, very good stdlib, strong IDEs/Debuggers, etc. but sadly interesting jobs like OSes, databases and compilers are way less common than in C++ world :(
Do you know about any sizeable open source projects written in C#, other than what Microsoft has produced? I rarely come across anything written in it.
It is not technology what holds .NET back. It is also not politics (nearly all languages have evil overlords). It is people who hold up to statements like: "I will not touch .NET with a 10-stick-pole"