10-4 Episode 3: ASP.NET WebForms 4.0 | 10-4

joechung

Nice explanation of the new ClientID feature!

Now that ClientID can be set, wouldn't it make just as much sense to use data binding to set its value? ClientIDMode=Predictable is nice but has limitations as was pointed out in the video. Setting a Suffix property is a nice shortcut if you have a data field amenable for use as a suffix, but if you don't, crafting a function that could, say, substitute spaces with dashes would also suffice.

A note about the video itself, you could have spent more time smoothing down the rough edges. Some of the monologue could have been re-recorded as it was worded a bit oddly. The transition from the end of the content to its summary was a bit jarring, too. The "3D cube" effect transition was cheesy; a simple blend or fade transition would have sufficed.

aL_
Rx ftw

dude, are you running ie6? Smiley

JonathanCarter

In reply to joechung

#Dec 31st, 2008 @ 4:36 PM

Thanks a lot for the feedback. I apologize for the "roughness" of the video itself. Jason and Brian are MUCH more experienced in the arts of Camtasia, so I'll work out the kinks. I was kind of going for a "conversation" feel, which is why I ended up not re-recording certain parts, but I'll definitely be more mindful of that.

I'll make sure to kill the cheesy cube rotate as well Smiley

As far as using some type of method to create your own client IDs instead of using the predictable method, you could definitely go that route. I didn't have time to show that, but it would be pretty intuitive.

JonathanCarter

In reply to aL_

#Dec 31st, 2008 @ 6:17 PM

The VPC I was running was XP and I was just using it as is Smiley

Stilgar

I wanna know if the ClienID features will be able to detect collisions. What if there are two entries with the same title? Are we gonna get some exception? Or maybe we can opt for an exception in the cases where we're not sure? Or if we're gonna use the new clientid features we must be sure that it is unique and there are no safeguards?