c# - Why keep code behind 'clean' and do everything in XAML? -

-

what benefit of keeping code behind 'clean'?

many times come across posts here trying equivalent in xaml instead of code behind. reason being want keep code behind 'clean'. correct me if wrong, not case that:

  • xaml compiled - baml - @ runtime has parsed code anyway.
  • xaml can potentially have more runtime bugs not picked compiler @ compile time - incorrect spellings - these bugs harder debug.
  • there code behind - or not 
    initializecomponent();
    has run , .g.i.cs file in contains bunch of code though may hidden.

    • is purely psychological? suspect developers come web background , markup opposed code.

    edit: don't propose code behind instead of xaml - use both - prefer binding in xaml - against making every effort avoid writing code behind esp in wpf app - should fusion of both out of it.

    1. designer perspective

    uis built designers using designer tools (expression blend , friends). if have kind of worklow, doesn't work if put significant amount of ui-related code in codebehind. @ least that's experience made. code , behavior/functionalty defines inacessable designer:

    • for part code executed @ runtime , not while designing. designer doesn't see full story while designing.
    • designers not programmers , have limited (if @ all) porgramming skills incapable of refining ui behavior defined there.

    additionally have made experience gets quite hard find way provide mocked designtime data (d:designinstance, d:designdata, d:datacontext) designer work if there codebehind.

    2. developer perspective

    ui-related code in codebehind (i assuming here unnecessary talk odds of putting domain logic in codebehind) code not reusable. code bound forever 1 specific usercontrol/window/page. if example instead write custom attached property or behavior resuablity plus make our desginers happy because can use too.

    all code put in codebehind code hard test. of course doesn't easier putting in xaml or in custom attached property. depending on type of functionality put in codebehind there cases have encapsulate in testable (reusable) classes.

    defining appearance , behavior in xaml tends less (as opposed questioners argument) error prone in code. can't make many mistakes in xaml can in code. if did wrong chances see right away in designer/visual studio. of course tools still can improve here. infact if additionally use resharper "incorrect spelling" miskates in xaml questioner mentions impossible make. code highlighted right away. sure standard tools pick up. xaml preferred way define ui in wpf , higher effort has been made microsoft assure works expected using code. infact have spent quite time debugging memoryleaks , runtime exceptions on code did ui related stuff , have been moved xaml little or no effort.

    if ease on codebehind abstinence there higher risk write clutterd , bad code. tempting put quick hack in codebehind. have sufferd consequences more once.

    using codebehind necessary. once used viewmodel driven uis there alomst never justifyable necessity codebehind. doesn't take effort put somewhere else. why bother?


    Comments

    Post a Comment

    Popular posts from this blog

    ASP.NET/SQL find the element ID and update database -

    -
    basically i've got update query runs when click submit button. i have asp:repeater in page layer inside this <asp:repeater id="dgbookings" runat="server" onitemdatabound="itemdb"> <itemtemplate> <div class="bookingscontent"> <div class="bookingdetails" id="<%# databinder.eval(container.dataitem, "booking_ref") %>"> <p class="infotext"><%# databinder.eval(container.dataitem, "adults") %> <asp:linkbutton onclick="editdetails" text="edit..." runat="server"></asp:linkbutton></p> <p class="infotext"><asp:linkbutton onclick="submitdetails" text="submit..." runat="server"></asp:linkbutton></p> </div> </div> </itemtemplate> <asp:repeater> and outputs ...
    Read more

    jquery - appear modal windows bottom -

    -
    i have modal windows in application, work fine <div id="modal" class="modal hide fade" tabindex="-1" role="dialog" aria-labelledby="mymodallabel" aria-hidden="true"> but when modal appears, appear top of windows, , want appear bottom the application joomla 3.0! , using template of meet gavern any idea? i found solution i modified de css in bootstrap .modal.fade { top:-25%; -webkit-transition:opacity .3s linear, bottom .3s ease-out; -moz-transition:opacity .3s linear, bottom .3s ease-out; -ms-transition:opacity .3s linear, bottom .3s ease-out; -o-transition:opacity .3s linear, bottom .3s ease-out; transition:opacity .3s linear, bottom .3s ease-out; }
    Read more

    c++ - Compiling static TagLib 1.6.3 libraries for Windows -

    -
    i having super hard time compiling , using taglib 1.6.3 in qt project. i've tried can think of. taglib claims supported through cmake i'm not having luck. furthermore, i'm confused kinds of files need qt libs! i've built *.a files, *.lib, , *.dll. understand far... believe since i'm working in windows *.lib want. no matter do, end "undefined references" taglib functions try use when try compile qt project. have tried mingw32, msys, visual studio 2008, , cross-compiling windows on linux. turning nothing. what makes less sense me if compile same taglib source qt on mac (g++ think?) works fine! somewhere in windows compilation procedures have going wrong. have been smacking face on desk 30 (on , off) hours trying figure out. since qt uses mingw must compile taglib same compiler? if compile *.lib's visual studio not compatible? are *.a libraries usable in windows? (assuming mingw) i'm still trying handle on c++ stuff, after reading coun...
    Read more