I've just download the RTM version of the AJAX Extensions, and I noticed there is no "Systen.Web.UI.Compability" namespace; these new controls are necesary in order to make work the validator controls. I've double checked two times using Reflector: in the RC version are there, but this namespace doesn't exist in the RTM version.

 please, somebody else could check this?

 fran

They have been removed for some reason.  I have cannot move to the new release due to this and other issues.  The validators don't fire which causes the PostBack to continue causing the behaviour of the validator to not work correctly.  The only work around I know of is to check if Page.IsValid in the event that fires the validation.

If you check Scott Guthrie's blog, there's a comment about this particular issue. Here's an excerpt:

"We are shipping a patch to ASP.NET that updates the built-in ASP.NET validation controls to work with ASP.NET AJAX.  Once this update is installed, they will work just fine."

Rudy

hi,

this could be true, but I've been testing the validators controls in the RC version with no problems. moreover, why this document

http://ajax.asp.net/documentation/Migration_Guide_RC_to_RTM.aspx

explains how to set-up the validators in the RTM version? is really strange such a big chang from the RC to the RTM version ....

 anyway, I'd like to hear the voice from somebody from the ASP team, in order to confirm what is going on ...

hello

well, the document says that you have to remove those entries from your web.config file, not add them.

ooops ... you are right

I also read the entries in Scott's blog, and I suppose we will have to wait until the ASP.NET update (I hope this doesn't mean the next service pack)

Once the tag mappings are removed things compiled fine for me. I ran into trouble using a MultiView control in the UpdatePanel. The first view seems to work fine with the validation controls, but the second view fails.

I'm not sure why a release build was shipped with what seems to be a significant change from the release candidate and moreover with an impending update to ASP.NET itself.

Anyhow, I'll continue to monitor and maybe someone can shed some additional light.

Rudy

And finally for anyone still wondering about this issue here is the interim solution until the Windows Update patch is available:

 

http://blogs.msdn.com/mattgi/archive/2007/01/23/asp-net-ajax-validators.aspx

 

Rudy

And finally for anyone still wondering about this issue here is the interim solution until the Windows Update patch is available:

 

http://blogs.msdn.com/mattgi/archive/2007/01/23/asp-net-ajax-validators.aspx

 

Rudy

WTF!

The workaround does work but is a pain in the arse...the tagMapping section has to be added to the <pages> element by the way which is omitted from the readme that goes with the workaround.

Something ain't right when you release a product with a major limitation like this that requires a workaround DLL to be compiled and copied into your bin folder.

I completely agree with Jason Hill, this is a dirty solution. I also understand this is a “temporal” solution, but I’ve never liked temporal solutions because they tend to be final solutions (I hope not)

I’m not an expertise in this field, but I liked the tagMapping solution of the RC version because the changes of the Validator controls were integrated in the AJAX dll itself; the solution of changing the ASP.NET dll (part of the framework) it looks to me to be more dangerous, because this implies a change in the framework. I guess Microsoft will release a Framework update (nobody knows when), then you will have to patch not only developers machines, but production machines. So, in order to make work Atlas on production, you will have to install the AJAX itself and the patch to the framwork; to me, is not really nice, moreover when you are dealing with hosting environment where you have “limited” control.

Documentation tell that u have to remove that entries from web.config

So remove that entries. It will work fine.

Wrong. Removing the web.config entries will eliminate the build errors but the validation controls won't work after partial postbacks.  You need to implement the workaround here to temporarily fix the validator problem until a framework patch is released.

I agree this isn't the ideal, but there were long-term pains associated with shipping a whole new set of validators.  The update to the original validator controls is in the pipeline to go out on Windows Update.  Any changes there go through extensive testing, but the delay won't be real long.

I suspect that it was a timing issue.  I think they were expecting the Windows Update that contained the updated custom validators to co-incide with the RTM release.

 

The validators are working again, but I am still having problems with "orginalWidth is Null" on popup extenders since installing RTM.