Coleman's .Net Nuggets

Little Nuggets from the .Net world.

  Home  |   Contact  |   Syndication    |   Login
  11 Posts | 0 Stories | 93 Comments | 0 Trackbacks

News

Tag Cloud


Article Categories

Archives

Image Galleries

Books

Documentation

Favorite Blogs

Favorite Sites

MSDN

Patterns

Programming

Resources

Tabbed Browing

Toolbox

I've been playing around with the validation controls and atlas…

The Atlas toolkit provides a Confirm extender… it is less than desirable. Canceling seems to have some event bubbling side-effects. The 2.0 OnClientClick is used… but a little differently. In the past, I have gotten away with OnClientClick="return confirm('Are you really really sure?')"… that doesn't seem to be the case… when you say ok, true is returned and client-side validation is not raised... therefore, the following nugget seems to play nice with all things considered…

<asp:Button ID="btnSomeAction" ValidationGroup="someAction" runat="server" Text="Submit" CssClass="button" OnClientClick="if (!confirm('Complete your action?')){return false;}" OnClick="btnSomeAction_Click" CausesValidation="true" UseSubmitBehavior="false" />

You may be saying, Coleman - Atlas provides mechanisms for validation… well yes and no.. Their examples show a lot of hand wiring… sources recommend staying with the 2.0 validation control. It would be a good bet that versions of controls down the road will just plug-in with the ATF... but until then, this seems to work... I'm not sure if it is a bug in the ANET or the ATF... but a gotch nonetheless.

Regards

Coleman

FYI: AT-las Framework and Asp.NET

posted on Tuesday, May 09, 2006 9:42 AM