Is it the right time to convert large .net based distributed SOA system into .net Core?

Question

We have a large business solution with some Windows Services, many WCF services, some SharePoint application and some ASP.NET MVC web applications those have been developed from nearly 10 years back. Currently we are using .net framework 4.0 .

Now we see .net open source platform is getting popular and it seems .net core will be the future of .net. In this situation, should we convert all the applications into .net core right now or we should wait for some more time (may be more than a years). Is .net core is stable enough for million dollar project's production yet?

Thanks in advance.

Answer 1

I have googled to find answers and found answers in dotnet platform documentation:

1. You should use .NET Framework for your server application when: Your application currently uses .NET Framework (recommendation is to extend instead of migrating)

2. WCF services implementation. Even when there’s a WCF-Client library to consume WCF services from .NET Core, as of June 2016, WCF server implementation is only available on the .NET Framework. This scenario is not part of the current plan for .NET Core but it’s being considered for the future.

3. Workflow related services: Windows Workflow Foundation (WF), Workflow Services (WCF + WF in a single service) and WCF Data Services (formerly known as “ADO.NET Data Services”) are only available on the .NET Framework and there are no plans to bring them to .NET Core.

As we are fully depended on WCF, we can not move to .net core right now(until wcf is is supported in .net core).

But in case of ADO.NET Data Services related feature to use, it must stay in .net framework.

Here is the document Choosing between .NET Core and .NET Framework for server apps