Mike-EEEMike-EEE

My feedback

  1. 321 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      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…

      Mike-EEEMike-EEE commented  · 

      Although not explicitly defined here, in addition to System.Xaml parity, the ask (assumption) is also ensuring that Xaml in UWP works like System.Xaml, in that it is in its own assembly and can be used in other applications (console, server-side, etc.). A conversation around this can be found here: http://forums.dotnetfoundation.org/t/nature-of-core-net-system-xaml/968

      Mike-EEEMike-EEE commented  · 

      Yet another incredulous limitation!!! Did someone actually get paid to make it this bad? ;)

      http://blog.jerrynixon.com/2014/07/lets-code-in-winrt-xaml-you-cannot.html

      Mike-EEEMike-EEE commented  · 

      Additionally, this assembly should also be self-contained and distributable, just like System.Xaml. Meaning, we should be able to use this assembly for Xaml serialization no matter where it's needed, whether it is in the client, server, anywhere... just like System.Xaml.

      Mike-EEEMike-EEE shared this idea  · 
    • 104 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        6 comments  ·  Microsoft Edge Developer  ·  Flag idea as inappropriate…  ·  Admin →
        Mike-EEEMike-EEE commented  · 
        Mike-EEEMike-EEE supported this idea  · 
      • 176 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          2 comments  ·  Windows Presentation Foundation (WPF)  ·  Flag idea as inappropriate…  ·  Admin →
          Mike-EEEMike-EEE commented  · 

          Oh man. OK. I had 6 comments on this thread, which seems a little silly now that I re-read them all. I have another post, so I will delete them all and replace with this one.

          First off, official recognition (but NOT commitment) towards this can be found here: https://github.com/dotnet/corefx/issues/5766

          You can also see a discussion around this very subject that has been going on for nearly a year here: http://forums.dotnetfoundation.org/t/nature-of-core-net-system-xaml/968/21

          Related vote:
          https://wpdev.uservoice.com/forums/110705-dev-platform/suggestions/7232264-add-markup-extensions-to-and-improve-winrt-xaml

          Also, here are current community efforts at a cross-platform port:
          https://github.com/SuperJMN/OmniXAML (nice write-up of features here: https://grokys.github.io/perspex/perspex-alpha3/ )
          https://github.com/cwensley/Portable.Xaml

          Finally, you can track this vote along with others via weekly reports found here:
          http://blog.developers.win/category/weekly-vote-reports/

          Incidentally, this console application was built/defined using Xaml, which can be seen here:
          https://github.com/DevelopersWin/VoteReporter/blob/master/DevelopersWin.VoteReporter.Application/Program.xaml

          https://imgflip.com/i/h6ho2

          Long Live Xaml!

        • 828 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

            84 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.

            Mike-EEEMike-EEE supported this idea  · 
            Mike-EEEMike-EEE commented  · 

            Thank you for your reply and engaging your users, Clint. Always nice to see a response from the mothership. :) I think the bigger/better question here is... why is a .NET technology not designed in such a way to allow *any* .NET language (present and future) to automatically and seamlessly interface with it? This seems to be a HUGE (embarrassing, really) oversight and makes the UWP group seem very out of touch or even a bit ignorant about the history of .NET and what it has enabled developers to achieve and the means by which they have been able to achieve it. Asking for a business case feels a bit aloof and circumspect in its own right. Developers want the FREEDOM to write their .NET applications in the language -- ANY language! -- that they desire. I think that is part of what is fueling this vote. I for one would expect whatever "fixes" this issue would fix it for *any* .NET language created going forward so that we never have to vote for something so obvious, expected, and instrumental again.

          • 59 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              under review  ·  9 comments  ·  Windows App Studio » Tools  ·  Flag idea as inappropriate…  ·  Admin →
              Mike-EEEMike-EEE commented  · 

              My thoughts exactly, btw. :P

              Mike-EEEMike-EEE supported this idea  · 
            • 228 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                8 comments  ·  Microsoft Edge Developer » Extensions  ·  Flag idea as inappropriate…  ·  Admin →
                Mike-EEEMike-EEE commented  · 

                OK I have spent the past few months putting a site together to better articulate my position around this concept and the general ask here. The core of the issue is that promoting HTML5/JS is an incompatible strategy with other Microsoft properties. Namely, the Windows Store and ... well, pretty much every technology under its IP portfolio, LOL. However, that doesn't mean it's incompatible or that there isn't a solution.

                You can view the series here: http://blog.developers.win/series/bridge-to-dotnet-ubiquity/

                Furthermore, the particular post that examines the expensive and divisive nature of promoting HTML5 alongside current .NET client application models and corresponding technologies can be found here:
                http://blog.developers.win/2015/10/the-broken-burned-bridge/

                Additionally, you can vote for the idea that will fix all of this: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/10027638-create-a-ubiquitous-net-client-application-develo

                Finally, this particular vote is a featured vote on Developers Win! http://developers.win/edge

                Whew. :)

                Mike-EEEMike-EEE commented  · 

                Wow, that was a LOT longer post than I thought it was, LOL!

                Mike-EEEMike-EEE commented  · 

                There has been some great discussions here and I (again) want to thank the Edge team and in particular David Storey for providing input and perspective. It's helped shaped my own thoughts around this and also made me realize that what I am after is bigger than the Edge group in particular (although they should most definitely be involved in some capacity).

                You make some good points below, Cyprien. This vote doesn't really capture the goal here, but it does attend to some of the primary issues. Everything you say makes sense through the lens of a web developer. And, if Microsoft was a web development company, then case closed, we're all happy and end of discussion.

                I would get to shut my face and you all would get to live in peace. :)

                However, it's not, and therein lies the problem. We have 15 years of .NET development to account for that currently does not enjoy the web ubiquity that you do. That is 15 years and thousands of organizations and 100,000s of developers who LOVE and PREFER their client application models JUST AS MUCH as you and other web developers do with yours. How are we (and Microsoft) to account for this?

                Again, if you write something in C# on the server side and another component that does the same thing in client-side JavaScript you have broken DRY and are adding costly (unnecessary) overhead to solutions and organizations.

                The primary issue here is that Microsoft does not have a bridge between the varying .NET client application models (WinForms/WPF/UWP) and the standards-compliant ubiquitous web. It is an enormously tremendous (expensive) hurdle and one that should be addressed altogether before every MSFT developer decides to bail altogether.

                And they will.

                Consider this: MSFT charges developers $19/year (and companies $99/year) to register for the Windows Store. Meanwhile, they are simultaneously promoting web-standards and HTML5 development through Angular and here with Edge.

                If a developer can develop a HTML5 application FOR FREE and is available more ubiquitously than a hosted store, then what incentive do they have to pay the $19 to register for access for a non-ubiquitous market?

                As awesome a job that the Edge team is doing, MSFT doesn't make money from its efforts or the standards it is promoting. In fact, MSFT doesn't make money from HTML5 at all, except if 1) Web Developers purchase Visual Studio (unlikely) or 2) Web Developers purchase and host on Azure (more likely).

                (Feel free to correct me here if I am wrong.)

                In fact, for every web developer out there, Microsoft is actually LOSING money because each one of those web developers are a potential $19 a year through the eyes of the Windows Store.

                Talk about self-sabotage. If I were a MSFT shareholder, I would be disturbed by this revelation.

                Again, this is a much bigger problem that is outside of the scope of this vote, but it is ultimately related. How do we bridge the divide between .NET client application models (which MSFT is now charging for registration as a featured business model) and the ubiquitous web (which is free and does not directly feed MSFT's bottom line)?

                I appreciate the conversation and do know I am wanting to make sure that MSFT is successful with its endeavors. I say that as someone who has invested nearly fifteen years of their life into its technologies.

                Mike-EEEMike-EEE shared this idea  · 
              • 82 votes
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  3 comments  ·  Universal Windows Platform » Framework  ·  Flag idea as inappropriate…  ·  Admin →
                  Mike-EEEMike-EEE commented  · 

                  This vote is part of a bigger vision that impacts a large part of Microsoft. You can see the Visual Studio vote for this vision here: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/10027638-create-a-ubiquitous-net-client-application-develo

                  Mike-EEEMike-EEE shared this idea  · 
                • 707 votes
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    26 comments  ·  Universal Windows Platform » Framework  ·  Flag idea as inappropriate…  ·  Admin →
                    Mike-EEEMike-EEE commented  · 

                    This vote is part of a bigger vision that impacts a large part of Microsoft. You can see the Visual Studio vote for this vision here: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/10027638-create-a-ubiquitous-net-client-application-develo

                    Mike-EEEMike-EEE commented  · 

                    UWP is not inherently tied to Windows and is actually very-well architected for cross-platform capability. Have you not seen all the interfaces that are used extensively throughout its API? Currently, these are all bound to the magnificent (and rather opaque) Curtain of COM, but it does allow for the design to be ported to other implementations.

                    But yes, I agree that this is not something that is trivial and will not happen overnight. I have resolved myself to waiting another 3-4 (at least) years before this can be considered a possibility. :) This vote is simply intended to start the awareness/conversation/direction. Thank you for your support and consideration!

                    Mike-EEEMike-EEE commented  · 

                    Exactly, Peter. The goal with this is exactly what you described: a direct, identical port of UWP to other platforms such as iOS and Droid (and others!). Xamarin.Forms is a fantastic technology in its own right, but it is middleware and it essentially caters to the target platform, ultimately rendering the application via the target platform's UI and controls, and corresponding UX. By contrast, the expectation here is that what you see on a Windows 10 device would look and work *exactly the same* on an iOS/Droid (or other!) device. The result essentially being a direct and perfectly identical port of UWP to other platforms.

                    By design, this implies that UWP is THE superior application paradigm when viewed against any competing options. Which it should be (and is???). This reasserts MSFT into its rightful place as an exceptional technology company, leading its developers into dominance and success, rather than following "standards" and leaving its developers in confusion and angst (ala Silverlight, and the inexcusable "just use HTML5" guidance/recommendation -- if you can call it that).

                    Mike-EEEMike-EEE commented  · 

                    Incidentally, by being open source and cross-platform, this idea would be possible to implement as well:
                    https://wpdev.uservoice.com/forums/110705-dev-platform/suggestions/7897380-expand-enable-universal-windows-platform-to-transp

                    Mike-EEEMike-EEE shared this idea  · 
                  • 154 votes
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      Mike-EEEMike-EEE commented  · 
                      Mike-EEEMike-EEE supported this idea  · 
                    • 707 votes
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        Mike-EEEMike-EEE commented  · 

                        1500+ votes, and it's been over a year since the last MSFT response on this... what is the status of this (popular -- currently rated #5) feature request?

                      • 1,865 votes
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          67 comments  ·  Universal Windows Platform » Framework  ·  Flag idea as inappropriate…  ·  Admin →
                          Mike-EEEMike-EEE commented  · 

                          Wow... 4700+ votes, and it's been over a year since the last MSFT response on this... what is the status of this (very popular -- currently rated #2) feature request?

                        • 4,236 votes
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            Currently, the platform provides a number of SMS Access from a system eventing perspective (as of Windows Phone 8.1), and Windows Phone supports sms backup/restore for consumers as part of the base OS (Settings → Backup). What we don’t provide is a backup API.

                            Using SMS events: Check out the Build 2014 session (http://channel9.msdn.com/Events/Build/2014/2-518) or MSDN docs on background tasks (http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh977056.aspx)

                            Although the capabilities are there from a consumer perspective (the core ask for the suggestion), I’m marking this as ‘Under Review’ for the API perspective. The team is aware of the ask and it is something that is being considered.

                            Mike-EEEMike-EEE commented  · 

                            Wow... 10,000 votes, and it's been over a year since the last MSFT response on this... what is the status of this (very popular -- currently rated #1 by FAR) feature request?

                            Mike-EEEMike-EEE commented  · 

                            Wow... 10,000 votes, and it's been over a year since the last MSFT response on this... what is the status of this (very popular -- currently rated #1 by FAR) feature request?

                          • 476 votes
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              12 comments  ·  Universal Windows Platform » Live Tiles  ·  Flag idea as inappropriate…  ·  Admin →

                              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.

                              Thanks!
                              Andrew – Windows Notifications

                              Mike-EEEMike-EEE supported this idea  · 
                            • 36 votes
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                Mike-EEEMike-EEE shared this idea  · 
                              • 309 votes
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  Mike-EEEMike-EEE commented  · 

                                  ... when a bug makes it on a feature request forum. :/

                                Feedback and Knowledge Base