This is all born from experience. I was working on a project I believed in and came to it after the stack used was crystallized and unchangeable. I ended up throwing my hands up in disgust and leaving.
This is all born from experience. I was working on a project I believed in and came to it after the stack used was crystallized and unchangeable. I ended up throwing my hands up in disgust and leaving.
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.
- .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?"
I dont know EF well but there is a rewritten core version