3 ms·
I'm finding library support quite good for .NET Core tbh. Not perfect, but it's not at all a barrier to adoption.
by james_s_tayler 8y ago
I'm finding library support quite good for .NET Core tbh. Not perfect, but it's not at all a barrier to adoption.
- pjmlp 8y agoTry to port any commercial component library to it like Telerik and friends, ODP.NET, WCF, EF 6, Forms, WPF. .NET Core 3.0 will fix some of the compatibility issues but not all of them, for example EF 6 will only be partially supported (VS DB tooling is not being updated for Core).
- james_s_tayler 8y agoYeah .NET Core 3.0 will address some of that, not all. I suppose for any brownfield development looking at switching across those things are the potential blockers at the moment. Especially things running EF where EF Core doesn't have a particular feature just yet. But EF Core development is cracking on at a good pace. Telerik and the likes I'm not so fussed about personally. I suppose DevExpress is another one on that list. I think front end component libraries like Prime-ng/PrimeReact are probably the way to go for the future of UI development for Line of Business applications. Overall I reckon in a couple of years there won't be much of those blockers left at all.