There is basically no reason to choose .Net Framework for a new project. There are a few reasons one may have to use .Net Framework, but unless the choice is forced, then one should always choose .Net Core. Even if you're only planning on supporting Windows OS. Even if you're making a library that has to be used by .Net Framework applications, one should still use .Net Core to create the library as .Net Core libraries that target .Net Standard 2.0 can be used by .Net Framework projects.
Or in shorter words: .Net Framework is dead, all new projects should target .Net Standard 2.0, .Net Standard 2.1, .Net 5, or .Net 6.
Sure. The Microsoft official runtime for .Net Framework was only written to work on windows, relying heavily on Windows' underlying Win32 api. It was unofficially possible to run .Net Framework code on Linux using the Mono project's Linux runtime and that was the foundation Microsoft used to create the cross-platform .Net Core.
It is also worth noting that no future .NET Standard versions will be "released." So build new .NET 6+ libraries to target .NET Standard support as needed until consuming code can be upgraded to match and we can rid ourselves of that mess once and for all.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There is basically no reason to choose .Net Framework for a new project. There are a few reasons one may have to use .Net Framework, but unless the choice is forced, then one should always choose .Net Core. Even if you're only planning on supporting Windows OS. Even if you're making a library that has to be used by .Net Framework applications, one should still use .Net Core to create the library as .Net Core libraries that target .Net Standard 2.0 can be used by .Net Framework projects.
Or in shorter words: .Net Framework is dead, all new projects should target .Net Standard 2.0, .Net Standard 2.1, .Net 5, or .Net 6.
This is also what I think (after what I read or heard). Do you know, why .NET Framework is limited to Windows?
Sure. The Microsoft official runtime for .Net Framework was only written to work on windows, relying heavily on Windows' underlying Win32 api. It was unofficially possible to run .Net Framework code on Linux using the Mono project's Linux runtime and that was the foundation Microsoft used to create the cross-platform .Net Core.
It is also worth noting that no future .NET Standard versions will be "released." So build new .NET 6+ libraries to target .NET Standard support as needed until consuming code can be upgraded to match and we can rid ourselves of that mess once and for all.