and ask him where the promised update to provide ajax validators is? It's been 5 months now since we were told it was going to come as an update via windows update
-
Follow
Oops, something didn't work.
Sign In to be begin to follow this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.Getting "follow" information
Start following this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.Removing your "follow"
Setting up your "follow"
Did you know you can
sign up for email notifications?
-
blowdart
Peek-a-boo
-
littleguru
<3 Seattle
Hehe
I wonder if somebody, who is attending Mix is reading the forums right now. -
irascian
Irascible Ian
Why not just email him? By all accounts he's very good at replying to email.
-
I just chatted with Matt Gibbs, and he says he's the one to corner to ask about this, not Scott.
He's prepping for his talk this afternoon about AJAX, and he'll address it there. -
FYI, Matt just told me that the latest ETA is mid-June.
-
blowdart
Peek-a-boo
smarx wrote:FYI, Matt just told me that the latest ETA is mid-June.
Thank you, most kind. It's been holding up a project I wanted to roll out internally.
-
JohnAskew
9 girl in pink sweater
Does section of a Web.config file look familiar?
Matt Gibbs has a workaround...<!-- The tagMapping section is for a CTP version of Ajax and must be commented out after installing the Ajax release version -->
<!--<tagMapping>
<add tagType="System.Web.UI.WebControls.CompareValidator" mappedTagType="System.Web.UI.Compatibility.CompareValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagType="System.Web.UI.WebControls.CustomValidator" mappedTagType="System.Web.UI.Compatibility.CustomValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagType="System.Web.UI.WebControls.RangeValidator" mappedTagType="System.Web.UI.Compatibility.RangeValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagType="System.Web.UI.WebControls.RegularExpressionValidator" mappedTagType="System.Web.UI.Compatibility.RegularExpressionValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagType="System.Web.UI.WebControls.RequiredFieldValidator" mappedTagType="System.Web.UI.Compatibility.RequiredFieldValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagType="System.Web.UI.WebControls.ValidationSummary" mappedTagType="System.Web.UI.Compatibility.ValidationSummary, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
</tagMapping>-->
-
blowdart
Peek-a-boo
JohnAskew wrote:
Does section of a Web.config file look familiar?
Matt Gibbs has a workaround...
yea I know, but as he'd said it was "short term" (hah, Microsoft timescales again) I'd resisted, hoping a proper supported version would come along
-
The sad thing is that the workaround probably pushed the actual fix which was originally scheduled for early April lower on the priority list.
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.