Patrick Hensly

My feedback

  1. 34 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Universal Windows Platform » Framework  ·  Flag idea as inappropriate…  ·  Admin →
    Patrick Hensly supported this idea  · 
  2. 350 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An always happy Friday as I just got the TFS complete email :) As this hasn’t hit an insider preview SDK, i’m going to mark this still as “working on it” still BUT … this will be coming to an insider build near you!

    This item heart is markup extensions. There is one item that will not be there however that is relevant to markup extensions, IServiceProvider. I created a new item for that but we are working on this item [https://wpdev.uservoice.com/forums/110705-universal-windows-platform/suggestions/19416094-iserviceprovider-for-markup-extensions-for-wpf-par]. We have created a new one and we are working on that (that includes IProvideValueTarget and INameScope) but feel we have enough to ship this and mark this larger work item done and we do point out in reference to more work items need to happen, namely the work around IServiceProvider.

    Also XamlServices.Load / Save isn’t directly related to markup extenstion so we’re viewing that…

    Patrick Hensly supported this idea  · 
  3. 874 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    92 comments  ·  Universal Windows Platform » Framework  ·  Flag idea as inappropriate…  ·  Admin →

    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.

    Patrick Hensly commented  · 

    Hi! Thanks for the response Clint. It seems to me that currently, .Net Native is not language agnostic like the rest of the .Net Framework. .Net languages normally compile to bytecode CIL (Comon Intermediate Language) which allows developers to use a multitude of languages to target the .Net Framework, from IronPython to F#. I think a better long term strategy would be to support all languages that go through the Common Language Infrastructure via compiling the emitted CIL in .Net Native.

    Patrick Hensly supported this idea  · 

Feedback and Knowledge Base