3 ms·
> .NET development happens behind clicks and VS interfaces. That hasn't really been the case since .Net Core (aka .Net 5/6) replaced .Net Framework. You can de
by Someone1234 5y ago
> .NET development happens behind clicks and VS interfaces.
That hasn't really been the case since .Net Core (aka .Net 5/6) replaced .Net Framework. You can develop entirely from the terminal if that is your choice or use Rider instead of Visual Studio if you want a cross-platform IDE.
> The resulting configuration ends up in REALLY unreadable XML files
You can now put the entire framework straight into the executables' directory, no more system-wide XML files. The concept of pre-installed .Net is legacy.
> This is all born from experience.
Of .Net Framework, which is deprecated.
- Beltiras 5y agoConsider this toast burnt for life. I am not about to trust anything coming from Redmond for life. This is in spite of having great respect for things coming from Microsoft Research. I'll happily use their toy OS for my games but if I intend to do serious work I will not interact with Microsoft offerings except ephemerally.
- Someone1234 5y agoLet's untangle this: - .Net Framework made a bunch of unfortunate design decisions. - You hated .Net Framework as a direct result. - .Net Core (aka .Net 5/6) fixed the problems, went OSS, went cross-platform, de-coupled from proprietary tooling. "Consider this toast burnt for life." I don't understand; if your disdain for .Net is meant to be technically founded then technical (and governance) improvements should address it but yet it doesn't here. Can you unravel why them essentially going through your laundry list of problems and fixing them one by one has left the "toast burnt for life?"
- Beltiras 5y agoYes. I have never been burnt by these other software tools. I like them better. They work as advertised and any new features are new features, not fixes.