Last post Oct 08, 2008 11:10 AM by javan15
Jan 29, 2008 01:49 PM|scott976|LINK
After following all steps mentioned in the 3.5 Extensions Preview readme, I am still getting the error
This is an existing application so the script manager has always been there. The script manager is defined on my page so I am not sure why I am getting this error. I have update all references, corrected web.config to use System.Web.Extensions, Version=220.127.116.11
Jan 29, 2008 02:47 PM|goodbox|LINK
are you sure your scriptmanager is above the controls that use it.
Jan 29, 2008 02:57 PM|scott976|LINK
yes everything was working until i tried using the extensions preview, i also got the ajaxtoolkit for 3.5
Jan 29, 2008 03:01 PM|goodbox|LINK
don't know what to tell you then, i read the extensions are going to be included in the actual release towards the end of the year, so there is probably still alot of stuff to work out. sorry o couldn't help more.
Feb 04, 2008 03:06 PM|gjadal|LINK
Is the control 'ace' an UpdatePanel Control?
Is the ScriptManager and UpdatePanel Control on the same page?
or are you using Master Pages..
Could you post your code here?
Feb 06, 2008 06:15 PM|omerkamal|LINK
if you are using master page then put the Scriptmanager just after From start tag.
Remove it from all other pages which are beeing embed in that master page.
Feb 23, 2008 12:40 PM|eggsarebad|LINK
Feb 24, 2008 09:12 PM|tgakk|LINK
I'm also having the same problem, but only on pages that have controls from the ajax control toolkit. I switched my 2.0 site to use 3.5 yesterday, installed the 3.5 extensions preview, followed all directions to switch to 18.104.22.168 in the web.config, and
downloaded the ajax 3.5 control toolkit. All the controls appear ok in the toolbox with correct versions. Pages that have a scriptmanager in them as well as just an updatepanel work fine--no complaints about the scriptmanager not being before the update
panel. Only having issues on pages with a scriptmanager and a control from the ajax control toolkit.
One thing I noticed as well is that if I go to a page that was using the cascadingdropdown and look at the page in design view, I can't see the cascadingdropdown anymore, although I can see the control definition in the source view. If I take out the TargetControlID
of the cascadingdropdown then it shows up again, but obviously won't work since the cascadingdropdown has no target control.
Any thoughts on either of these issues? My whole point in going to the extensions preview was because I was trying to use the cascadingdropdown control (which works fine), but if a user clicks the back button on the browser, it either retains the original
values of the first time they went to the page, not the new values they selected, or if I have multiple sets of cascadingdropdowns on the page, then sometimes one set doesn't retain any of the selected values. I was hoping that the browser history option
in the previews would allow me to maintain viewstate of these cascadingdropdowns when the user clicked the back button to go back to the page the cascadingdropdowns were on. So if there is a solution to get the cascadingdropdowns to remember its selected
values when the back button is clicked without using the asp.net 3.5 extensions preview, then that would be good as well.
Thanks in advance.
Feb 25, 2008 12:12 PM|Semenenko|LINK
I had the same problems. There are some tricks how to solve these:
1. Check the AjaxControlToolkit.dll in your bin directory. I think you'll find the previous version of it. So - you should replace this with the latest version.
2. Check the project references (right click on website icon in solution explorer - proterty pages menu item) - you should add the reference to the AjaxControlToolkit.dll in your bin directory.
I suppose this is the VS 2008 feature - it inherits some staff from previous version of Visual Studio and tries to resolve all possible troubles. Not very successfull in this case. This probably happens when you opening your page in design view for the first
time (not sure). Sometimes it asks something like: "There is AjaxControlToolkit.dll ... do you want to replace it?".
Feb 25, 2008 04:18 PM|eggsarebad|LINK
Under my project references I have the AjaxControlToolkit.dll version 3.0.11119.25533. Everything looks perfect in design view. It only gives me problems when I try to load the page.
Feb 25, 2008 04:32 PM|eggsarebad|LINK
Wooo! I got it working. I started a new project and copied the web.config into my old project!
Feb 25, 2008 10:58 PM|tgakk|LINK
Just to report back, I did the same as eggsarebad and created a new empty extensions web project and copied over parts of that web.config to my existing websites web.config and then it started working--no more scriptmanager errors. However, I still can't
see the cascadingdropdown controls in the design view although they are working properly now at least when my website runs. Wonder if that is a bug in the extensions.
Now if I could only get the history to work with my cascadingdropdowns when the back button is clicked, I'd be in good shape...
Feb 26, 2008 03:27 AM|Semenenko|LINK
It will be very interesting to compare these configs. I think it can be helpful.
Jul 02, 2008 01:02 PM|meSync|LINK
Look closely and make sure the complition section in your web.config has all three of the system.web.extensions references. the first points to version 3.5 the other the to version 1.
This worked for me.
Oct 08, 2008 11:10 AM|javan15|LINK
I deleted it and then it worked fine