I've recently converted a project from .NET to .NET core 1.1, and I encountered some issues along the way. This is a documented list, so I can keep track of when they get addressed.

Problems

• There is no support for embedding languages (Dynamic Language Runtime doesn’t work) so I can’t use IronPython to embed a python interpreter for Scripting/Orchestrations. IronPython looks a bit poorly anyway, the mailing list is really quiet. (http://stackoverflow.com/questions/31753746/ironpython-for-net-core)

• There’s no support for authenticating against Active Directory yet (!) (https://github.com/dotnet/corefx/issues/2089)

• There's no support for defining an [Index] against an attribute in my EntityFramework database object yet, I have to do it somewhere central in a big list. Yuk. (https://weblogs.asp.net/ricardoperes/missing-features-in-entity-framework-core-1 and https://github.com/aspnet/EntityFramework/issues/1698)

• [ExcludeFromCodeCoverage] doesn’t exist (http://stackoverflow.com/questions/39907175/exclude-class-or-method-from-code-coverage-in-net-core). In fact, code coverage doesn't work at all.

• No support for sending emails, but there are other options out there (http://dotnetcoretutorials.com/2017/01/11/sending-receiving-email-net-core/)

• Entity Framework 7 (the version that works in .net core) doesn’t support Lazy Loading yet (and it seems a long way off). You have to manually load foreign key objects. (https://github.com/aspnet/EntityFramework/issues/3797)

• Can't raise exceptions from webapi services to control the response. I used to be able to do throw new HttpResponseException(this.Request.CreateErrorResponse(HttpStatusCode.NotFound, lEx.Message)); but that no longer works and there doesn't seem to be nice replacement.

Benefits

• Swagger works, through Swashbuckle.