Christopher Bennage - All Comments

Windows Client Developer Roundup for 3/8/2010

Microsoft Weblogs — Thu, 11 Mar 2010 21:11:51 GMT

This is Windows Client Developer roundup #14. This is my first Roundup on my new blogging platform .

re: Silverlight Challenge: Creating a DependencyProperty

Christopher Bennage — Wed, 10 Mar 2010 15:17:41 GMT

Correct. The default needs to be a double. The exception throw is a little vague, and I stared at this for about 10 minutes before it occurred to me. :-P

Regarding the 'readonly', it doesn't cause an exception but it's a good idea. It was an accident that I omitted it in the example.

re: Silverlight Challenge: Creating a DependencyProperty

Hadi — Wed, 10 Mar 2010 08:48:40 GMT

the only change needed is "new PropertyMetadata(0.0)", readonly is not necessarily needed.

dotNet News

Cadred (dotNET) — Tue, 09 Mar 2010 21:23:21 GMT

dotNet News

re: Silverlight Challenge: Creating a DependencyProperty

Jason Young — Tue, 09 Mar 2010 21:16:19 GMT

I can see two issues, the dependency property declaration should be marked readonly and the value passed to the PropertyMetadata should be a double, i.e. "0.0".

re: Silverlight Challenge: Creating a DependencyProperty

Hüseyin Tüfekçilerli — Tue, 09 Mar 2010 21:15:12 GMT

Use

new PropertyMetadata(0d)

instead of

new PropertyMetadata(0)

re: 1 Simple Step for Commanding in Silverlight

Christopher Bennage — Tue, 09 Mar 2010 15:43:23 GMT

The element names and the method names have to stay in sync. The binding is evaluated at runtime. If obfuscation only changes one, it will break.

re: 1 Simple Step for Commanding in Silverlight

jim — Tue, 09 Mar 2010 14:55:52 GMT

Do you know how this would respond to obfuscation?

re: 1 Simple Step for Commanding in Silverlight

Mike Stokes — Mon, 08 Mar 2010 22:27:37 GMT

Awesome post :) Anyway to remove code from the code-behinds and into binding has got to be a big winner for everyone!

re: XAML Attributes on Separate Lines

Christopher Bennage — Mon, 08 Mar 2010 21:43:45 GMT

Here's the place to encourage the Blend tend to support this:

expressionblend.uservoice.com/.../500231-option-to-position-each-attribute-on-a-separate-li

re: XAML Attributes on Separate Lines

Christopher Bennage — Mon, 08 Mar 2010 14:54:03 GMT

@Steve Unfortunately, Blend does not have this feature. (At least, I can't find it). I spend a lot of time in Blend myself, and I usually keep the same files open in VS so that I can reformat them there. Far from ideal ...

re: XAML Attributes on Separate Lines

Steve Crane — Mon, 08 Mar 2010 12:19:54 GMT

A nice option that I would like to suggest to my colleagues. One question though; is there a similar option in Expression Blend? The bulk of our XAML is created by a designer and there's little point turning this on for VS if Blend can't do the same thing.

Social comments and analytics for this post

uberVU - social comments — Sun, 07 Mar 2010 04:48:17 GMT

This post was mentioned on Twitter by ke4ktz: GReading: XAML Attributes on Separate Lines http://goo.gl/fb/UjBf

Cheap soma.

Cheap soma. — Sat, 06 Mar 2010 03:51:46 GMT

Soma buy soma cheap soma soma online. Watson soma cheap. Cheap soma.

re: XAML Attributes on Separate Lines

Khalil Muhammad — Wed, 03 Mar 2010 10:00:47 GMT

Well written. I totally agree with you. Using such a formatting scheme makes it easier to deduct the logical structure of UI elements defined in the XAML.