More XAML Designer Less XAML Typing

Play More XAML Designer Less XAML Typing

Description

In this episode, Robert is joined by Jon Chu to explore how good the Visual Studio XAML Designer and Blend are these days. Robert's New Year's resolution is to spend less time typing XAML and more time using the designers. Jon shows several examples of how you can build a XAML app and not have to type the XAML.

Resources

Embed

Download

The Discussion

  • User profile image
    bcnz

    Really looking forward to XAML edit and continue! You have also convinced me to use Blend for the VisualStateManager (learned it recently, been doing it by hand with XAML) and for Storyboards. Excited!

  • User profile image
    issam

    Hi,

    any news about the xaml designer XDesProc hang bug ?

  • User profile image
    john

    I downloaded the zip file from GitHub, but I get 800+ errors. What did I miss?

  • User profile image
    rati_dzidzi​guri

    We all understand this is a little bit time consuming job to create one, but What about XAML Designer for Xamarin Forms? More and more developers choose Xamarin for cross platform mobile app development.

     
  • User profile image
    rogreen

    @ratige: You will have to ask Xamarin about a designer for Xamarin Forms.

    Robert

  • User profile image
    rogreen

    @john: If you build the project do they go away? Do you have the Windows SDK 10.0.10586 installed?

    Robert

     

  • User profile image
    rogreen

    @issam: Can you provide more details on this bug? Has it already been reported to us? Is it something that you are experiencing? Feel free to email me at rogreen at microsoft dot com with additional information.

    Thanks!

    Robert

  • User profile image
    Jim Klep

    Now that you acquired Xamarin, please add support for Xamarin Forms on designer!

  • User profile image
    ChrisSnazell

    I appreciate the desire to hide the ugly reality of XAML's incredible levels of verbosity behind tooling but honestly these tools aren't up to the job.

    Blend is probably the most byzantine & impenetrable Microsoft application I've ever come across. There's a long and glorious tradition of developer tools having poor UX but Blend is one step beyond. You'd have to be clairvoyant to use it.

    The VS design surface is handy for a quick preview but it's still much, much, more efficient to crank XAML by hand. When you can't recall the semantics of a property use the properties pane just like you would with the designer.

    Both tools are pretty appalling when you've got XAML resources in a shared project with symptoms ranging from erroneous error reporting to the design tool crashing. 

     

  • User profile image
    birbilis

    since VS2015's Blend is using VSX from what I understand, how hard would it be to eventually integrate the two?

    I'd like to have Blend's panes inside Visual Studio itself and have some premade window layout called "Blend" to switch the IDE to just show the current Blend layout. Still I would be able to make my own layouts by say just adding the Timeline/Storyboard to my current layout etc.

    Have been hoping this for years - I really don't get the dichotomy and switching back and forth between different tools. When people use tabs in browsers to avoid multiple windows, how does one expect them to ALT+TAB between tools? Personally I even hate switching the layout, I want to configure one with some autohidable and some pinned panes and keep using it

  • User profile image
    ShaunRussell

    At 27:50 when Robert asks about Intellisense for state names when using GoToState(), there's actually 3 ways you can reference the state. The way shown in the video is using a string, which doesn't have any compile checking and if the state name changes you have to manually update it. The other ways are either using the C# nameof operator, or type in the state's name (because it's an object) and use its Name property.

  • User profile image
    anon

    Continue in this line. It is ok to write XAML code from time to time. But most old devs coming from Visual Basic and Win Forms are used to create UI just dragging and dropping components and moving into designer and is much more productive. I think is something that made VB and Winforms great and so easy to start with for anyone.

  • User profile image
    anon

    Also, please add support designer for XamarinForms

  • User profile image
    Donna

    Hello. This XAML Designer feature looks awesome! But... how do you get to it?

    I've created a Xamarin Cross-platform solution in C# in VS2017. I cannot find how to activate the XAML Designer window. Where is it? This video starts with it already up, not showing details how to get there.

    Can anyone lend a hand on setting me straight? I'd much rather create UIs with drag-n-drop than hand-code.

  • User profile image
    rogreen

    @Donna: The XAML Designer is available for Windows 10 and WPF applications. There is currently no support for Xamarin Forms. 

    Robert

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.