Hacker News Reader

Comment by Lord_Zero | Hacker News Reader

Most major libraries have been ported. What are you using?

* EO.pdf for converting HTML to PDF. It uses a headless Chrome instance to render the page and then converts it to PDF. We have a lot of complex page layouts, such that switching rendering engines wouldn't be a simple tasks either.

* Server-side WCF endpoints. We're currently exposing WCF endpoints, which we must maintain for our current users.

EVO PDF has a .NET Core version

http://www.evopdf.com/netcore-html-to-pdf-converter.aspx

There are a lot of first-party Microsoft dependencies that have not been updated and probably never will be. For instance, I do a lot of work with the Skype for Business SDKs, which are old and have D-level engineering assigned to them.

Skype for Business is going away too. As soon as we moved to Teams I stopped opening my SfB client completely.

Unfortunately Teams has no usable extension API that would allow the funtionality of the old UCMA and UCWA apis.

Some of it has already (Beta) moved into the Microsoft Graph super-API: https://developer.microsoft.com/en-us/graph/docs/api-referen...

Presumably, as Teams gets closer to eating S4B it will catch up on more of the rest.

Adomd lib for communicating with SQL Server Analysis Services (from MS) has not been ported. WCF is also absent from .net core which makes migrating to .net core much harder for existing projects.

I'm not sure (haven't tried it), but I believe there are few tricks where the assembly can be loaded on .NET Core _but_ the called APIs in the assembly must of course be present.

WCF support is in Core, we use it extensively to communicate to legacy systems. It is missing some features, like WCF Relays. As for hosting WCF services on Core, we've been trying to distance ourselves from WCF in favor of other technologies.

I think OP is referring to server-side WCF in Core, see also this discussion: https://github.com/dotnet/wcf/issues/1200. As we're currently exposing WCF endpoints, this is also something that's holding us back.

Very niche, proprietary libraries

ExcelDNA, Google OR-Tools, COM apis.

I didn't hear about Google OR-Tools before now, but they seem to support .Net Core: https://developers.google.com/optimization/install/dotnet/so....

COM support is coming to .NET Core 3.0

Reply on news.ycombinator.com