It’s great to see that XAML for Live Tiles is so highly requested!
In Windows 10, we created Adaptive Tile Notifications, which partially addresses this issue. Adaptive is a lightweight XML way to define your tile notification’s appearance. It isn’t as powerful as XAML, and it isn’t animated, but it’s a step in the right direction. The MSN Weather app uses Adaptive to create their rich and beautiful live tile.
Learn more about Adaptive here: http://blogs.msdn.com/b/tiles_and_toasts/archive/2015/06/30/adaptive-tile-templates-schema-and-documentation.aspx
In the future, we’ll definitely look at how we can make Live Tiles even better, potentially by supporting XAML. There are performance and other implementation issues, but we definitely understand the need for it.
Andrew – Windows Notifications
310 votesworking on it · 30 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
Markup extensions are a must for great Xaml. Xamarin Xaml supports them and so does Silverlight. Open source is preferred and expected these days. From another thread, vote here too: https://github.com/dotnet/corefx/issues/5766
102 votes0 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
This is a great idea. We’ll start looking at the feasibility of this to see if we can get this on a backlog iteration.
232 votes11 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
This is great feedback. We are excited about the Xamarin acquisition and the .NET ecosystem around cross-platform apps. We are currently looking at this and similar feedback on how we can improve the experience of working with both Xamarin.Forms and UWP implementations of XAML.
Yes, consolidate all Xaml flavors and take the best from all models, please. This vote and the GitHub issue have my upvote!!!
F# team just posted an update on their GitHub. https://github.com/Microsoft/visualfsharp/issues/1096
This is still a work in progress. One key thing from that post is some of these features and fixes have already been underway for months. While we’ve been investigating F#-specific issues in .NET Native, the team has continued to improve .NET Native. One feature known as “universal shared generics” is likely to have improved .NET Native’s support for F#, even without that being an explicit goal of the feature.
Good to see the efforts here. F# is pretty great and looks like it is a cheaper way of developing applications. I might make the jump from C# to F# soon... granted all the good tech supports it!