Entries:
Comments:
Discussions:

Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Discussions

DeathByVisualStudio DeathBy​VisualStudio If we all believed in unicorns and fairies the world would be a better place.
  • Rift vs Hololens vs ps4 VR is MS going to lose out.

    I think the real question is will VR become something that people feel like they need or will it be a fad like 3D TV and Kinect?

  • Annoying "Get W10" updates

    Here's one more for the pile... 

  • OneDrive problems

    I'd recommend TwoDrive. It's twice the fun!

  • Xamarin now Open Source and included with VS

    A big win for Microsoft on this move. With Windows Mobile/Phone/whatever pretty much dead they had to provide a way to keep their tech relevant for mobile developers. 

  • MS buying Xamarin

    Awww... Cans I hava YEAH!!!?...  YEAH!!!?, YEAH!!!??, YEAH!!!???

     

  • MS buying Xamarin

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

    YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!YEAH!!!

     

  • Microsoft Kill Off Windows Phone

    , bondsbw wrote

    @DeathByVisualStudio:  I don't know about the ribbon control (never liked it enough to even try) but adaptive triggers in UWP seem to be pretty simple.  Tell it what causes the state to trigger (windows size above a certain point), and what to change.

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    <VisualState x:Name="Wide">
        <VisualState.StateTriggers>
            <AdaptiveTrigger MinWindowWidth="900" />
        </VisualState.StateTriggers>
        <VisualState.Setters>
            <!-- Keep SplitView pane always showing inline -->
            <!-- Hide the Hamburger, it's useless here -->
            <Setter Target="MySplitView.DisplayMode"
                    Value="Inline" />
            <Setter Target="MySplitView.IsPaneOpen"
                    Value="True" />
            <Setter Target="HamburgerButton.Visibility"
                    Value="Collapsed" />
        </VisualState.Setters>
    </VisualState>

    That's oversimplified. When you have a complex business app you'll have a sh1t ton of controls and user concerns to deal with. Alternatively you can say to the user "Less is more, F off", "Yes I moved your cheese, get over it", "I don't care how many clicks it takes to get to the center of a tootsie-pop", etc.

  • Microsoft Kill Off Windows Phone

    Just thinking out loud... UWP's adaptive/auto layout reminds me of the ribbon control. You have to be pretty detailed oriented to get the ribbon to handle size changes in a way that make sense. I would surmise it's even more difficult when you apply that requirement to the entire layout of the screen as with UWP. That said reactive web layouts are difficult to create for the same reasons. 

    All-in-all I believe the idea is great; it's the cost of implementation that's not so great. Maybe that's were Microsoft can win back some developer mind-share -- show that UWP's adaptability is easier to implement and maintain that building a reactive web app.

  • Microsoft Kill Off Windows Phone

    , cheong wrote

    @DeathByVisualStudio: There are potential non-technical side of problem for having Apps in multiple platform.

    Having In-App purchase regulation in iOS (section 11) and WP (section 5e) at the same time effectively make "I want to build App for both platform, and make features bought in any of the platform automatically switched on too when login in App of other platform with same account" breach of contract. App developer have to choose to:

    1) sell the App as a whole;
    2) seperate user accounts for different platform;
    3) App builders who want to use micropayment strategy just choose the platform with bigger marketshare.

    Now spare me some time while I curse whoever make such bureaucratic roadblock...

    Valid points but I would hope that you could abstract much of that out. That may mean you have a ridiculously complex build process but once setup it shouldn't be too bad.

  • Microsoft Kill Off Windows Phone

    While Islandwood is useful I don't think the honeypot of UWP is enough to get developers to port and maintain two codebases (the original iOS and the ported UWP). I still believe that Microsoft's best bet would be to acquire Xamarin and offer their technology along with UWP free with Visual Studio. Then developers have a better chance of porting with Islandwood, dumping their native code, and staying in the Microsoft eco-system for development. Not everyone would do it because it's not that simple and may not work for more complicated apps but it would certainly get more traction than UWP alone.