3 ms·
Historically spoken, it was the WinXP security mess which forced the .NET team to take over WPF and then as a consequence build the different CoreCLR for Silver
by oaiey 9y ago
Historically spoken, it was the WinXP security mess which forced the .NET team to take over WPF and then as a consequence build the different CoreCLR for Silverlight. That however was killed by the same guy who killed Flash. Mr. Jobs from Apple. The Win8/Mobile Team Just harvested the most modern technology at that time (CoreCLR).
There is a nice talk about it, somewhere on YouTube.
- pjmlp 9y agoWin 8 sucked for .NET developers regarding API compatibility, because it required lots of incompatible changes, which are the reason Windows 10 FCU is the first UWP version to be finally compatible with .NET Standard 2.0 (4.6.1). Then there was the whole 8.0, 8.1 with UAP, and finally UWP transitions. The two only good things from UWP for .NET devs were finally getting .NET Native, which should be there since 1.0 given the Delphi roots of Anders, and the COM Runtime model that was in the genesis of .NET (formerly known as Ext-VOS). I think the talk you refer to, is one from OS research group at MSR.
- oaiey 9y agoNo the talk is from the .NET Rocks guys. https://youtu.be/IqWar6cEWsA https://youtu.be/IqWar6cEWsA UWP/UAP is a new UI stack from the Windows team BOUND to a CoreCLR. That is different with the existing .NET UI technology stacks. Additional, the CoreCLR and its more modern Assembly packaging (System.Runtime vs mscorlib) made the code difficult to share (recompile or PCL). This is solved now by the .NET Standard.
- pjmlp 9y ago> UWP/UAP is a new UI stack from the Windows team. That is different with the existing .NET technology stacks. Which is what I meant with "mess created by Sinofsky regarding .NET, UWP and C++/CX.". I do have UWP experience since WP 8. Thanks for the link about the talk.