I support this proposal fully. The tooling itself is free, already distributed with Windows 10 SDK.
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.
Thank you for using Visual Studio and for your commitment to improving it. We are currently evaluating whether we will be able to include this into the product.
This issue I gave 1 vote because fundamentally I agree with the original issue poster (Denis). But I prefer smoother migration to DX10 first, and then DX 11 in the future.
The adoption of DX10 will be easier to implement than adoption of DX11 into WPF, as the migration from technological standpoint of DX9 to DX10 itself is easier than DX9 to DX11.
Furthermore, DX11 capable/supported hardwares (display adapters) are not that many in current market, as far as I know (on January 2015).
I also vote this one. I gave 1 vote, because WPF is going to be deprecated by Microsoft, in favor of Windows Store apps... :(