150 votes7 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
Thanks for this feedback, this is an area that is being discussed on how we might improve the overall XAML verbosity syntax as well as make this easier for customers of ISV controls.
9 months to start a discussion or to even acknowledge a very obvious request. Dysfunctional with a capital D. Visual Studio team needs to take over this group and show them how to get things done.
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.
310 votesworking on it · 30 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
Wow over 14 months to simply say you will not strive to make your product like one that was better than it created nearly a decade ago? And this is with a high-ish vote count. I do not even know where to start with that. Does anyone over there even care?
From the looks of it, "on the backlog" looks like where ideas go to die. Some of these issues are four years and counting:
This group has a rep for sititng around and collecting a paycheck. Now I see why. Guess we'll have to go to Visual Studio or open source for this.
If anyone is interested, there is an open issue on GitHub to port System.Xaml to the CoreFX libraries:
With the Xamarin acquisition this is all but certain now. Furthermore, another vote in Visual Studio has been marked as under review: https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/10027638-create-a-ubiquitous-net-client-application-develo
This one takes this a step further and asks for a web/WASM bridge for .NET.
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.