341–350 of 374 posts
Been away from .NET for many years. In those days, business logic was largely represented as procedural code using classes for organization, manipulating recordsets or datasets. Is that still the case?
In that case, go back to PHP or where-ever you come from ;-)
.NET 5, .NET Standard, .NET Framework, .NET Core, ... now .NET 8. It's so confusing still.
It's actually pretty easy if you're new to .NET. If that's the case, it's just .NET 8 and forget about everything else. .NET Core was renamed to .NET 5, which became the mainline .NET. .NET 8 is simply the latest version. .NET Standard is intended to be a common layer to help bridge between .NET Framework and .NET Core and .NET 5+. It shouldn't be used outside of that context. .NET Framework is the old, Windows-only…
Earlier quoted context omitted.
.Net 8 is supported 3 years, . Net Framework 4.8 presumably longer. Confusing.
.NET Framework is part of Windows. That means it is very stable and supported for a very long time. But it is also not possible to evolve it further. That is why the .NET team forked it to make .NET Core, which is cross platform and installs versions side by side. This is what evolved into .NET, most recently .NET 8.
That means "stable" as in "it is not going to change".
But from a developer perspective, binding redirects, brrrrrr.... Also, source-level framework debugging tends to break every so often. It is obvious their focus is on the new .NET.
Earlier quoted context omitted.
If you spend 20 hours fixing something that wouldn't occur with the paid toolchain, at what price does it become worth it to skip those 20 hours when they're not directly applicable to what you're trying to accomplish?
When you literally don't have $20 in your account. Then you can spend 100 hours and it's still worth it.
Earlier quoted context omitted.
> The main issue I have had is if you are trying to get into the .Net Ecosystem without spending money. I suggest not trying to do this. You can certainly make most of .NET8 work with a pure OSS toolchain, but your overall development experience is going to be destitute compared to that of the official tool chain. To be clear - I think paid alternatives, such as Rider are fantastic too, but even so I've had some trou…
> At the end of the day, you have to ask yourself about what your hourly rate is. If you are going to spend a 20 hour premium per week bandaging up a "free" .NET toolchain, whereas the official, $100/m stack costs you 1-2 hours, which one actually costs you more? Also the official stack is supposedly supported, which means you can contact Microsoft if you have an issue. In practice, you get some underpaid outsourced…
Earlier quoted context omitted.
> At the end of the day, you have to ask yourself about what your hourly rate is. If you are going to spend a 20 hour premium per week bandaging up a "free" .NET toolchain, whereas the official, $100/m stack costs you 1-2 hours, which one actually costs you more? Also the official stack is supposedly supported, which means you can contact Microsoft if you have an issue. In practice, you get some underpaid outsourced…
I teach for a living, mostly people of poor backgrounds, and a lot of them in the Third World. I understand your argument (and I buy some tools myself), but I can't tell them to use paid tools because the cost may be too high in the local currency and it adds up fast.
As full stack .net dev, I am so disappointed every “who is hiring” thread. I would be game to join a trendier group of like minded devs but if you get one .net posting you are lucky, and it’s most likely rockstar. :(
Been away from .NET for many years. In those days, business logic was largely represented as procedural code using classes for organization, manipulating recordsets or datasets. Is that still the case?
You can use micro-ORMs like Dapper, but I don't how you would do anything else than classes to represent your result sets unless you want to stuff everything in a dynamic ExpandoObject (which you can). In that case, go back to PHP or where-ever you come from ;-)
Earlier quoted context omitted.
You can use micro-ORMs like Dapper, but I don't how you would do anything else than classes to represent your result sets unless you want to stuff everything in a dynamic ExpandoObject (which you can). In that case, go back to PHP or where-ever you come from ;-)
You can use an object domain model to model a complex system. Something more common in say Java than .NET with its traditional “wizard” based tooling legacy. Worth looking up if all you know is recordsets and datasets.
I'm looking at a language to write simple executables with or without GUI and that are not too verbose or too complicated. A bit like a compiled python :) Would .NET 8 be a good challenger ? I previously didn't consider it because the compilation to binary was looking more like an experiment, and the example I've seen were quite verbose (in a java way).
Personally I use F# for console apps, with ahead-of-time if startup latency is important, yeah. Works fine for me! (Ahead-of-time is much harder with F# though, because .NET idiomatically leans heavily on reflection thanks to C#'s influence, and reflection is banned in AOT. C#'s workaround is source generators, which F# does not support except very unofficially. I therefore find myself stamping out boilerplate for e.…
This was my first experience while getting started in the .NET ecosystem. I wanted something similar, I wanted to build small console tools/services and F# looked cool but hit the reflection issues too soon.
I mostly use crystal and golang, but both have their own issues. Hopefully F# improves with time to be fully usable with AOT!