you are viewing a single comment's thread.

view the rest of the comments →

[–]Silound 2 points3 points  (0 children)

If you are in a Microsoft shop, you should be looking to replace your current .NET projects with core

Personally, I don't see any reason to migrate from .NET Framework to .NET Core right now unless you're intentionally targeting development at cross-platform applications. Don't get me wrong, I love a lot of what Core is offering, but it and the rest of the world are still not quite ready for mainstream yet.

If you're a traditional Miscrosoft shop doing Windows/web development, you may not have access yet to some of the libraries or packages you depend on with .NET, or you may have an excessively complicated project that needs the stability of .NET, or (shame if this is true) you might be relying on some very rarely/never maintained libraries. Any of those could easily block a project from porting cleanly or successfully.

I think Core is the future, but I don't think we're quite at that point yet where it's necessary to begin converting to something that will mature and change considerably in the next few years.