Misfit Geek

Why are using Adobe Flash as your Media Player not Silverlight

boooooo use silverlight…dogfooding…

Sure – point me at a GOOD audio only player !

Thanks – but there is no release yet, can you hook me up with a sample ?

Thanks John – I’m already working on Number 2 !

RE: Episode #1 of the Misfit Geek Podcast is now LIVE !

The first podcast in my new series is now live at misfitgeek.com/…/misfit-geek-pod

RE: Episode #1 of the Misfit Geek Podcast is now LIVE !

If you are looking to follow this series, be sure to subscribe to my RSS feed at http://feeds.jasongaylord

Hi Joe, loved the first podcast as you covered many of the issues i have nowadays with webforms. It looks like most the issues i have, have now been addressed however there is 1 biggie which has annoyed me.

It’s around 2 way databinding. 1 way databinding works perfect for me as i can eval anywhere i want my data to be displayed. If you use 2 way databinding you can’t format this data as easily on display (wrapper functions are not supported with Bind although you can still use the standard optionally parameter which is gives you some limited functionality).

The other issue with 2 way databinding is that if the name of the property on my Object is different from the name of the parameter on my insert/update method then i have manually bind the databind via the OnInserting/OnUpdating events of the data source control. This is particularly annoying when you have a complex type (bind doesn’t support this but eval does). For example, say you have the following entities:

User

- int | UserID

- string | Name

- Address | Address

Address

- string | Line1

- string | Line2

Now in my formview i can easily bind the line 1 of the address using eval by saying Eval("Address.Line1") but this does not work with Bind therefore i have to manually add this via the code behind which is abit of a pain and can be even more annoying when your objects are bigger and you have to worry about nullable fields which gets handled automatically by 2 way databinding normally.

I have long thought about the solution to this problem and i think the best way to solve it would be to display the data in the current method of using Eval("Property") but then have an extender control specifying the name of the Update/Insert parameter, eg:

<asp:TextBox ID="txtLine1" runat="server" Text=’<%# Eval("Address.Line1") %>’ />

<asp:BindExtender ID="beLine1" runat="server" Name="MyUpdateMethodParameterNameLine1" ControlID="txtLine1" />

Note: MyUpdateMethodParameterNameLine1 is used to make the point that i’d like to be able to give my insert/update parameter a completely different name from the property it is bound too.

Surely this wouldn’t take that much extra time to add in now and providing the current 2 way databinding method is left in place then it would be backwards compatible.

Appreciate if you could pass this on. Thanks

my comment and question was not posted.