Related Links

There is a bug with ASP.NET Ajax Beta 1.0 when an AutoCompleteExtender control is used within a page which inherits from a master page. I havnt included an example because its dead easy to recreate the error using a basic web service.

The AutoCompleteExtender works fine in a normal web form yet if I move the controls to a page which inherits from a master page and include the script manager in the master page it has a javascript error when the page loads - (Sys.ArgumentNullException). I
have seen many people raise this issue and they are just being told to include [ScriptService] at the start of their web service class, however this does not resolve the issue. My web service includes this attribute yet it still does not work but in a normal
web form with no master pages involved it works like a dream. Any help or advice would be greatly appreciated.

Web service is not the issue although because the extender works fine in a normal page.

I think its something to do with the javascript that ATLAS is generating cos the JS error appears the moment the page loads. Perhaps its not taking account of the name mangling which occurs when a page has a master page.

I apologize I didn't read closely enough the first time to recognize this was a javascript error and not a ASP.Net error.

I do not know if this helps or not, but I was having the exact same situation under a master page (which is all I use and I have the autocompleteextender working) as well. If you are using a panel as your Completion List Element then you need to make sure
that it is actually visible. I have read another post on here and a few blogs that say it is supposed to be set to not visible by default....but this only caused js errors. It seems that once you set the CompletionListElementID to the panel the js will handle
making it not visible....hope this helps..

No problem Josh, I double checked the visibiltiy of the panels and stuff but still broke :-(. Are you using the latest ATLAS Beta 1 release because I have seen a number of posting from people with the same problem as me and no fixes anywhere so I am pretty
confident this is a bug that has been introduced in the Beta.