News for hackers. Stuff that matters.
Re:ASP.NET Core 3.0 will only run on .NET Core by Lord_Zero on Friday November 02, 2018 @11:38AM (#18363780)
Most major libraries have been ported. What are you using?
Re:ASP.NET Core 3.0 will only run on .NET Core by bouke on Friday November 02, 2018 @02:04PM (#18365233)
* 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.

Re:ASP.NET Core 3.0 will only run on .NET Core by DenisM on Saturday November 03, 2018 @01:11PM (#18371273)
Re:ASP.NET Core 3.0 will only run on .NET Core by thrower123 on Friday November 02, 2018 @11:57AM (#18363992)
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.
Re:ASP.NET Core 3.0 will only run on .NET Core by joeax on Friday November 02, 2018 @12:08PM (#18364108)
Skype for Business is going away too. As soon as we moved to Teams I stopped opening my SfB client completely.
Re:ASP.NET Core 3.0 will only run on .NET Core by thrower123 on Friday November 02, 2018 @12:11PM (#18364142)
Unfortunately Teams has no usable extension API that would allow the funtionality of the old UCMA and UCWA apis.
Re:ASP.NET Core 3.0 will only run on .NET Core by WorldMaker on Friday November 02, 2018 @01:45PM (#18365085)
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.

Re:ASP.NET Core 3.0 will only run on .NET Core by polskibus on Friday November 02, 2018 @11:48AM (#18363874)
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.
Re:ASP.NET Core 3.0 will only run on .NET Core by rblatz on Friday November 02, 2018 @12:22PM (#18364259)
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.
Re:ASP.NET Core 3.0 will only run on .NET Core by bouke on Friday November 02, 2018 @02:11PM (#18365291)
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.
Re:ASP.NET Core 3.0 will only run on .NET Core by sebazzz on Friday November 02, 2018 @12:14PM (#18364175)
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.
Re:ASP.NET Core 3.0 will only run on .NET Core by pingec on Friday November 02, 2018 @11:41AM (#18363801)
Very niche, proprietary libraries
Re:ASP.NET Core 3.0 will only run on .NET Core by cm2187 on Friday November 02, 2018 @12:34PM (#18364400)
ExcelDNA, Google OR-Tools, COM apis.
Re:ASP.NET Core 3.0 will only run on .NET Core by svick on Friday November 02, 2018 @04:31PM (#18366465)
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....
Re:ASP.NET Core 3.0 will only run on .NET Core by benaadams on Friday November 02, 2018 @04:56PM (#18366666)
COM support is coming to .NET Core 3.0