A Major Silverlight PITA, and Two Annoying 3.0 Limitations

Why not join our community?, there are 11 users online

home
silverlight
view story

DotNetKick.com is an open-source project. Please report any bugs and let us know your great suggestions. Currently running svn revision 620 (rss)

Kick Spy!, Kick Zeitgeist and Kick Widgets

9
kicks

kick it

A Major Silverlight PITA, and Two Annoying 3.0 Limitations

published 5 months, 23 days ago, submitted by Lear 5 months, 27 days ago

rapidapplicationdevelopment.blogspot.com — Did you know Silverlight implements the Visible property as an enumeration not a Boolean? That leads the author to find two frustrating .Net 3.0 limitations: No ByRef Extension Methods, and no ByRef Automatic Properties.

2 comments | category:

Silverlight | Views: 156 | Get KickIt image code

tags: Silverlight | tag it

Everyones tags:

Your tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

Lear - rev4bart - Lord - talisharon10 - josephf - rishitraykhanna - samdnp - Reman - adeel41

Comments:

Nice overview of the problem in Silverlight. I always ask myself...why did they do it this way, this is one of those limitations :)

posted by rev4bart 5 months, 27 days ago

ByRef extension methods would be very cryptic, since you do not expect c.DoSomething() to replace c.
IValueConverter solves Visiblity problem in WPF, I am not sure if Silverlight supports them, but if it does, it is just a minor annoyance, not a PITA.

Anyway you can 'ByRef' properties by doing ExtensionMethods.SetVisible(value => IsPanelVisible = value, true), which is a bit longer but works fine.

posted by ashmind 5 months, 23 days ago