birbilis

My feedback

  1. 113 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  ·  Visual Studio IDE » .NET  ·  Flag idea as inappropriate…  ·  Admin →
      birbilis commented  · 

      MSHTML isn't going away. Desktop apps need to keep on working, can't break them with Spartan. The limited WebView control could use the Edge engine of Spartan and made available apart from WinRT to desktop apps too. Most however desktop apps I think will prefer the classic control

    • 2,939 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        18 comments  ·  Visual Studio IDE » UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
        birbilis commented  · 

        I was trying the other day to fix the issue with WPF not supporting visual inheritance (that is deriving a XAML-based UserControl from another XAML-based one), as Silverlight does (to reuse XAML assets as linked files from a common folder at my WPF and Silverlight project versions in http://ClipFlair.codeplex.com), by comparing the generated designer code (.xaml.cs file) of WPF and Silverlight and tweeking the 2nd one to use at WPF too. I hit a roadblock because WPF requires BAML (so I probably need to add a custom compilation step to generate such since I don't want WPF to generate the backend code for me [because of the visual inheritance not being supported]).

        However, through that exercise of comparing the .xaml.cs files generated for WPF and for Silverlight, I noticed the 1st one contains lots of attribute declarations that must be useful (or already used?) for XAML debugging. Wonder why the Silverlight version doesn't have such too

        birbilis commented  · 

        @rev5: when you say find the source code that generated a graphical component, do you also mean those added dynamically? I guess that can be quite tricky, unless they use the new C# stuff that tells a method who has called it to keep UI debug info internally at each control when debugging (to remember what method generated it).

        Usually UI is generated declaratively via XAML and that's what you can see and edit with XAMLSpy (dynamically). I think it can also persist now your changed back into the original XAML files of your project which is very handy

        birbilis commented  · 

        Have you guys seen XAML Spy (http://xamlspy.com/)? It's evolution of former Silverlight Spy

        It's amazing software, have been recently using it with ClipFlair Studio Silverlight app (http://ClipFlair.net / http://ClipFlair.codeplex.com) and it really helped me nail down some strange UI artifacts I was seeing

        Hope Microsoft gets ideas from it, or buys it / hires that guy

      • 2 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          0 comments  ·  Visual Studio IDE  ·  Flag idea as inappropriate…  ·  Admin →
          birbilis shared this idea  · 
        2 Next →

        Feedback and Knowledge Base