3 ms·
.NET Core is where it is now, and the UI story is (as always) evolving FAST. Make sure to build a good separation between back- and frontend, and be ready to sw
by alkonaut 5y ago
.NET Core is where it is now, and the UI story is (as always) evolving FAST. Make sure to build a good separation between back- and frontend, and be ready to switch
If you are lucky and you are making not-very-complex UIs, you can make a thin wrapper using some of the "newer" frameworks. If you make heavy/classic UI's you will probably have to go for WPF or a Third party framework instead.
- bpicolo 5y ago.NET 5 nixed the "Core" naming I think. It's all .NET now. (They kept "ASP.NET Core" for libraries)
- alkonaut 5y agoAh right. ".NET" is it. Not "Framework" (Which no one ever pronounced before) i.e. 4.X
- mattferderer 5y agoThis sounds like good advice no matter what language/framework