Comments on: XAML guidelines and best practices

By: Computer Deals

Computer Deals — Sun, 03 Jan 2010 21:50:11 +0000

My brother in law would appreciate this post. We were just speaking about this. hehe

By: Corey

Corey — Mon, 12 Oct 2009 19:55:30 +0000

Thanks Anthony. True MVVM encourages Xaml without names, however, when working with Blend it’s still important to have each element with a name. Much like working in Photoshop you name Layers, Blend should be the same way.

By: Anthony

Anthony — Mon, 12 Oct 2009 16:29:52 +0000

I agree with most guidelines except the one about naming every element. If you follow MVVM, the best way to know you are on the right track is when your View (the XAML) no longer needs any x:Names or event handlers, because you rely complely on bindings to the ViewModel properties.

By: mknopf

mknopf — Thu, 23 Apr 2009 20:38:18 +0000

nice article Corey, thanks for the info

By: XAML Guidelines And Best Practices | Switch on the Code

XAML Guidelines And Best Practices | Switch on the Code — Wed, 11 Feb 2009 18:10:12 +0000

[...] XAML Guidelines And Best Practices Source: 85turns Excerpt: [...]

By: esh

esh — Wed, 11 Feb 2009 11:44:32 +0000

@steveThen you will name control GenderCombo, GenderButton or GenderCheckBox :). I was using prefixes before but turned a year ago to using longer suffix because it is easier to read and understand. What means btn, txt, cnt, ddl… and others prefixes?

By: Silverlight Travel

Silverlight Travel — Tue, 10 Feb 2009 13:13:49 +0000

To work based on best practices is every time a good ideaPeter Loebeö

By: Silverlight Travel » XAML guidelines and best practices

Silverlight Travel » XAML guidelines and best practices — Tue, 10 Feb 2009 13:12:07 +0000

[...] more here [...]

By: Steve Buchok

Steve Buchok — Tue, 10 Feb 2009 13:11:58 +0000

I agree with most of the guidelines with the exception of the prefix. Giving a prefix not only quickly gives you a list of the same type of controls on a page it also tells you what you can do with that control. What happens if you have a control on the page called Gender? This could be a dropdownlist, radio button or checkbox (or something else all together) by having a prefix you immediately know how to set the information or get the information. It is the same reason you have a prefix for vairable names. There is no reason you can’t make something descriptive and use a prefix. One last thing, if developers and designers have to work together they are both going to have to adapt to how the other works, which means trying to stick to each others standards.

By: Darren

Darren — Tue, 10 Feb 2009 07:34:20 +0000

I prefer the formatting you describe too. It’s as important for me to be able to read it as anyone else. Also it’s a pain to keep scrolling left to right to see everything too when editing. Now, if only blend would format like that…