3 ms·
If you burned it to the ground and started over, that may have also been on you. The amount of code that was capable to run unchanged between 6.5 (CF), 7 (Silve
by WorldMaker 8y ago
If you burned it to the ground and started over, that may have also been on you. The amount of code that was capable to run unchanged between 6.5 (CF), 7 (Silverlight-like-CF), 8.1+ (.NET Core) was very high. Sure, there was a ton of churn between 6.5's horrid WinForms fork, 7's Silverlight XAML, 8's .NET Core-ish version of Silverlight-ish XAML, and 10's WinRT XAML, but if the majority of your app wasn't just UI code-behind (at which point, why not rearchitect to a good MVVM pattern or relative?), transitioning that XAML should have been simple.
- ThrowawayR2 8y agoPerhaps he's referring to the Win32-style apps that were the norm on Windows Mobile 6.0 and earlier? There was an huge number of apps (for that era anyway) that were obsoleted by the transition away from that paradigm.
- WorldMaker 8y agoYeah, it is possible that it could have been written in C/C++ Win32-ish COM. Though Microsoft was never subtle in Windows Mobile <= 6.5 in telling developers they should only use .NET Compact Framework's System.Windows.Forms fork on that platform, as opposed to Desktop Windows where it has seemed far too subtle in their framework recommendations (partly because they were far too divided internally in the Desktop space). As I said, from that perspective, most Compact Framework code should have worked in Silverlight other than UI rewrite because the Silverlight runtime wasn't far from CF. It needed a recompile, but not necessarily a rewrite, in theory. (Though obviously theory and practice are very different things.)