I still had the old beta 1 install so i uninstalled beta 2, reinstalled beta 1, then removed the beta 2 toolkit dll from my project and re-inserted the beta 1 toolkit dll (i had it saved also). After that I just re-built the project and it works again.
------------------------------------------------
Jeff Turner
Don't forget to mark the correct answer for your
question to help out future visitors!
The problem is definitely not a result of VS not being installed, but I wonder if it's to do with the location of the Visual Studio 2005 folder?! I uninstalled the Extensions, and then reinstalled and them and Microsoft.Web.Extensions.Design.dll appeared!
Could not load type 'Microsoft.Web.UI.Design.ExtenderControlDesigner' from assembly 'Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
Its been reported that some actually do an install - then uninstall - then new re-install of the BETA2 bits (no idea why just they have stated it works)..it will add the references to VS the second time...
Others have stated doing a reboot solved the issue....
Additionally - make sure you MODIFY the WEB.CONFIG - as there are new changes such as registering the new SCM - the new Extensions designer - etc... see the toolkit example website for a full working config and make appropiate changes..
I've tried to role back to Beta 1 but I'm still having issues, can someone tell me the version number for the beta and the control toolkit? I have 1.0.61025 for the beta and 1.0.61020 for the control toolkit but my project gets this error....
[InvalidOperationException: An extender can't be in a different UpdatePanel than the control it extends.]
Microsoft.Web.UI.ExtenderControl.RegisterWithScriptManager() +504
Microsoft.Web.UI.ExtenderControl.OnInit(EventArgs e) +95
AjaxControlToolkit.ExtenderControlBase.OnInit(EventArgs e) +133
System.Web.UI.Control.InitRecursive(Control namingContainer) +459
System.Web.UI.Control.InitRecursive(Control namingContainer) +271
System.Web.UI.Control.InitRecursive(Control namingContainer) +271
System.Web.UI.Control.InitRecursive(Control namingContainer) +271
System.Web.UI.Control.InitRecursive(Control namingContainer) +271
System.Web.UI.Control.InitRecursive(Control namingContainer) +271
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1746
Ok, this has been more frustrating than trying to get hair to grow back on top of my head - and seriously I can't afford to lose any more of it...
SO, yes - I marked the issue resolved as it seemed to work for most people - however - on my system(s) I found I had to do the following just to get the toolkit to build:
Remove project references to the Microsoft.Web.Extensions*
Do so by right clicking the projects references tab in the solution explorer pane.
Expand it
delete the current references for Microsoft.Web.Extensions (should only be one).
right click and choose Add Reference
click the .Net tab - scroll about 3/4 way down
ADD all three entries for :
Microsoft.Web.Extensions , Microsoft.Web.Extensions.Design, and Microsoft.Web.Preview
you should do this by NOT doing the browse for file - it will be in the .Net tab. Yes, you can still do the copy the dlls - but the references should be done in manner above - it will first search global assembly cache and then local bin if not found.
Recompile the project...
There is a bug at least with Team Studio that it will ref older dlls even if you have removed them using the uninstaller. You'll know this is your case if you try to compile and when the page is loaded you get a Sys error and nothing actually works (in
IE at least - in FF2 - nothing works in terms of the UI but no errors ...So, that means in your own projects assuming you did all the right things for the web.config - you'll need to perform that process for EVERY project that uses the ajax components (core,
ctp and toolkit)...
Last but not least - missing in the web.config is:
Without nothing works...in terms of the ajax scenario....
Additionally - turn off the debug and trace -in web.config - even in the release version of the toolkit - its enabled and will cause issues with some of the controls...(see my previous posts on issues with trace etc..)
gbianchi
Member
110 Points
22 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 07, 2006 07:17 PM|LINK
tfsmag
Contributor
3467 Points
686 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 07, 2006 07:42 PM|LINK
Jeff Turner
Don't forget to mark the correct answer for your
question to help out future visitors!
gbianchi
Member
110 Points
22 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 07, 2006 07:43 PM|LINK
vbuitte
Member
30 Points
6 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 07, 2006 07:48 PM|LINK
I dropped the dll from my VS machine into the bin directory of the website living on my server (2003) and it worked!
This is hopefully an interim solution.
Thanks for the advice![:)]
sesh
Member
5 Points
1 Post
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 07, 2006 08:27 PM|LINK
mike963
Member
14 Points
4 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 07, 2006 08:36 PM|LINK
same problem
Could not load type 'Microsoft.Web.UI.Design.ExtenderControlDesigner' from assembly 'Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
installed using gacutil
copied files onto bin directory
have VS installed
Stuck - back to beta 1 I guess
Mike
Mike
jodywbcb
Contributor
4482 Points
985 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 07, 2006 08:50 PM|LINK
Its been reported that some actually do an install - then uninstall - then new re-install of the BETA2 bits (no idea why just they have stated it works)..it will add the references to VS the second time...
Others have stated doing a reboot solved the issue....
Additionally - make sure you MODIFY the WEB.CONFIG - as there are new changes such as registering the new SCM - the new Extensions designer - etc... see the toolkit example website for a full working config and make appropiate changes..
My Blogs on .Net 2.0 and Ajax
http://csk.wbcb.com
http://ArtbyJody.com
nprudhoe
Member
61 Points
17 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 08, 2006 10:18 AM|LINK
I've tried to role back to Beta 1 but I'm still having issues, can someone tell me the version number for the beta and the control toolkit? I have 1.0.61025 for the beta and 1.0.61020 for the control toolkit but my project gets this error....
[InvalidOperationException: An extender can't be in a different UpdatePanel than the control it extends.]
Microsoft.Web.UI.ExtenderControl.RegisterWithScriptManager() +504
Microsoft.Web.UI.ExtenderControl.OnInit(EventArgs e) +95
AjaxControlToolkit.ExtenderControlBase.OnInit(EventArgs e) +133
System.Web.UI.Control.InitRecursive(Control namingContainer) +459
System.Web.UI.Control.InitRecursive(Control namingContainer) +271
System.Web.UI.Control.InitRecursive(Control namingContainer) +271
System.Web.UI.Control.InitRecursive(Control namingContainer) +271
System.Web.UI.Control.InitRecursive(Control namingContainer) +271
System.Web.UI.Control.InitRecursive(Control namingContainer) +271
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1746
jodywbcb
Contributor
4482 Points
985 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 08, 2006 12:08 PM|LINK
Ok, this has been more frustrating than trying to get hair to grow back on top of my head - and seriously I can't afford to lose any more of it...
SO, yes - I marked the issue resolved as it seemed to work for most people - however - on my system(s) I found I had to do the following just to get the toolkit to build:
Remove project references to the Microsoft.Web.Extensions*
Do so by right clicking the projects references tab in the solution explorer pane.
Expand it
delete the current references for Microsoft.Web.Extensions (should only be one).
right click and choose Add Reference
click the .Net tab - scroll about 3/4 way down
ADD all three entries for :
Microsoft.Web.Extensions , Microsoft.Web.Extensions.Design, and Microsoft.Web.Preview
you should do this by NOT doing the browse for file - it will be in the .Net tab. Yes, you can still do the copy the dlls - but the references should be done in manner above - it will first search global assembly cache and then local bin if not found.
Recompile the project...
There is a bug at least with Team Studio that it will ref older dlls even if you have removed them using the uninstaller. You'll know this is your case if you try to compile and when the page is loaded you get a Sys error and nothing actually works (in IE at least - in FF2 - nothing works in terms of the UI but no errors ...So, that means in your own projects assuming you did all the right things for the web.config - you'll need to perform that process for EVERY project that uses the ajax components (core, ctp and toolkit)...
Last but not least - missing in the web.config is:
<add verb="GET"
path="ScriptResource.axd"
type="Microsoft.Web.Handlers.ScriptResourceHandler"
validate="false"/>
Without nothing works...in terms of the ajax scenario....
Additionally - turn off the debug and trace -in web.config - even in the release version of the toolkit - its enabled and will cause issues with some of the controls...(see my previous posts on issues with trace etc..)
My Blogs on .Net 2.0 and Ajax
http://csk.wbcb.com
http://ArtbyJody.com
Dmitriy99
Member
5 Points
1 Post
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 08, 2006 01:38 PM|LINK