First post here, so please excuse my newbieness. I am reading and learning about Core .NET. I am hearing some conflicting explanations around this so I am looking for clarification here.
By some accounts, it sounds like Core .NET is a streamlined version of the .NET Framework, and you can add traditional .NET Framework assemblies into your solution based on need.
Other accounts make it sound like this is a complete overhaul and traditional .NET Framework assemblies will not be compatible at all (or will at the very least require a re-compile of some sort).
The kernel of my questioning/concern has to do around System.Xaml. So, if you can assuage my anxiety here and provide a solution/direction/explanation in the “new” Windows 10 / .NET Core paradigm, I will be most grateful.
To start with, WinRT implementation of Xaml is an inferior translation of the System.Xaml assembly offering. This is primarily reflected in the fact that markup extensions are not allowed/supported in WinRT. This is truly an unfortunate oversight, as 90% of Xaml’s power (and fun!) lies within these incredible creations.
(For context, markup extensions are provided in WPF, Silverlight 5, and Xamarin.Forms – a non-MSFT technology!, but not WinRT.)
I am basically looking to see/verify if we will be able to use System.Xaml (and other .NET Framework assemblies) with Core .NET, or if this expected to be unsupported.
Secondly, if System.Xaml is not available for/compatible with Core .NET, it would be great to know:
- How difficult it would be to port System.Xaml over to the new Core .NET (as an open-source project, perhaps).
- (Trickier to answer here as this is out of the scope of Core .NET) If markup extensions are accounted for, corrected, and supported in the new Xaml offerings for Windows 10 App Model (I have a feeling I will just have to be patient and wait for //build for this answer ).
Thank you for any assistance/clarification/insight.