4 ms·
I am curious what specific features you are using in .NET Framework 4.7x that are not accessible in .NET Core. We use 'legacy' APIs like System.Drawing and Sys
by bob1029 8y ago
I am curious what specific features you are using in .NET Framework 4.7x that are not accessible in .NET Core.
We use 'legacy' APIs like System.Drawing and System.DirectoryServices from .NET Core without any issues today - https://docs.microsoft.com/en-us/dotnet/core/porting/windows-compat-pack https://docs.microsoft.com/en-us/dotnet/core/porting/windows....
Although, we exclusively target Windows platforms right now (RID == win-x64). We are considering replacing these Windows-only deps with cross-platform alternatives in the future (e.g. Novell LDAP and Mono drawing) so that we can start looking at Linux as another hosting option.
I have even had reasonable success with retargeting 3rd party libraries to .NET Standard 2.0 without much coding effort. It's mostly just *.csproj XML soup management.
- pingec 8y agoFor example C++/CLI
- ToFab123 8y ago<I am curious what specific features you are using in .NET Framework 4.7x that are not accessible in .NET Core. Windows Communication Foundation (WCF)
- ToFab123 8y agoTo expand on this. As I understand Microsoft has started to create a new version of WCF for .NET core (or 5 as it is called now). I should a multi-year development project to do this, because it can no longer be "Windows" Communication Foundation since it also must work on Linux. They same goes for EWT tracing which is the logging mechanism you can use. That also has to be cross platform. So for some years to come, I (on some projects) are "stuck" with .NET 4.X until WCF and EWT has been re-architectured.
- pjmlp 8y agoNot at all, they just made it official that we are forced to rewrite those apps.
- ToFab123 8y agoSince much of the banking world is heavy users of WCF, Microsoft has no other option that to implement WCF in. Net 5 unless they want to loose the banking industry. I did come across a post from one of the WCF products managers who said that they are working on a cross platform solution but it will take some (much) time before that has been completed. Cannot find this post, but I consider it safe to say that WCF for .net 5 is coming and that I am stuck util it does as there really is no alternative to using WCF
- pjmlp 8y agoI have mentioned multiple times in other threads, ODP.NET, WCF, EF6 designers, Blend, C++/CLI, CMS like Sitecore and other commercial components.