A) Install the Beta 2 on your webserver. Then REBOOT IT. Restarting the web service did not work for me, I had to reboot it (this fixed your issue aa0606 - presumably the new DLL got registered but the old one was still in memory? They moved UpdateProgress
out of CTP and into the base install it seems).
that's what I was thinking as well, and was planning on rebooting my server last night. however, before I did, I checked the page again and the page was working properly, so I guess somehow the old dll got flushed out of memory and replaced by the new one.
I was finally able to get things working here's what I ended up doing.
uninstall beta 2 completely
get everything working again in beta 1 and re-build project.
install beta 2 again
clear out toobars in vs and delete reference to old toolkit in solution.
add new toolkit dll to project and to toolbar
look at your web.config and the new toolkit sample website web.config side by side, make any changes to references etc. you see between your web.config and the sample website web.config.
build project and run, everything works fine.
publish project to a folder on your drive
move project to web server
manually add microsoft.web.extensions.design to bin folder on webserver.
Everything works now... what a trip to the dentist!
------------------------------------------------
Jeff Turner
Don't forget to mark the correct answer for your
question to help out future visitors!
So, if you've installed the Nov 6 beta 2 and CTP, you have the .dll(s) you need for plugging-into your project's bin and ftp'ing to your host server. Simply use your start menu, all programs, Microsoft ASP.NET 2.0 AJAX Extensions, ASP.NET Ajax Extensions Assembly
and Script Library - contains .dll(s). Is that correct?
fari enough, i am not sure why it does not install the Microsoft.Web.Extensions.Design.dll when using msiexec installer, but i will gladly provide more info if it helps.
the machine that we installed Atlas dll file to is:
windows xp pro sp1 (this is a corporate machine and we have issues installing service pack 2(something to do with Standard Operating Environment error), this is why we cannot use VWD Express)
.Net Framework 2.0
the Event viewer showed a bunch of MSI installer events such as
Product: Microsoft ASP.NET 2.0 AJAX Extensions -- Configuration completed successfully.
Product: Microsoft ASP.NET 2.0 AJAX Extensions -- Installation completed successfully.
Product: Microsoft ASP.NET 2.0 AJAX Extensions -- Configuration failed.
Product: ASP.NET 2.0 AJAX Extensions -- Removal completed successfully.
from my attempts to get stuff working and ultimately failed.
I had the problem with No Microsoft.Web.Extensions.Design as well and fixed it completely with a few hours work. I have VWD on XP Pro and no VS.
I couldn't find an Uninstall for Atlas Extensions (even though it should have been there), so I did a search for Ajax and deleted every folder and file on my machine with Ajax ;-)
I also uninstalled the Ajax CTP (which did have an Uninstall)
I uninstalled Microsoft Web Expressions Developer (who knows, I don't use it and wanted to fix the problem).
Then, when I installed AJAX 1.0 Beta 2 again I had the file, and had an uninstall. Once I unzipped the Ajax Control Toolkit I simply used the file menu to open the website and everything worked perfectly.
Error 1 N:\Inetpub\wwwroot\Default.master: ASP.NET runtime error: Could not load file or assembly 'Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file
specified. (N:\Inetpub\wwwroot\web.config line 43) N:\Inetpub\wwwroot\Default.master 1 1 N:\Inetpub\wwwroot\
In the web server as well as the machine I used to develop the site do have all the files, System.Web.Extensions.dll, System.Web.Extensions.Design.dll, AJAXExtensionsToolbox.dll, and Microsoft.Web.Preview.dll. I also copied all of these files into my bin
folder and I still received this error. It kept refferring to this line in the web.config file.
Here's what I found out. I have two machines that uses the same project on the same web server. This machine does not have this error when compile so I take a look at it's .Net Framework 2.0 Configuration in the Assemly Cache and I found the Microsoft.Web.Extension
listed under the Assembly Name but on the machine that has this compiled error, I do not find this assembly listed in the Assembly Cache. So my question is, how do I add it in the Assembly Cache? I tried the "Add an Assembly to the Assembly Cache" option but
I do not know which file to add. Help is still much appreciated.
rb_jlm
Member
50 Points
10 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 09, 2006 01:02 PM|LINK
I posted a response on another message about this error. My experience was that it was pretty straight forward.
Re: Beta 2 problems - Could not load type 'Microsoft.Web.UI.Design.ExtenderControlDesigner'...
Hope helps.
rb_jlm
Member
50 Points
10 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 09, 2006 01:02 PM|LINK
I posted a response on another message about this error. My experience was that it was pretty straight forward.
Re: Beta 2 problems - Could not load type 'Microsoft.Web.UI.Design.ExtenderControlDesigner'...
Hope this helps.
aa0606
Member
32 Points
10 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 09, 2006 02:20 PM|LINK
that's what I was thinking as well, and was planning on rebooting my server last night. however, before I did, I checked the page again and the page was working properly, so I guess somehow the old dll got flushed out of memory and replaced by the new one.
tfsmag
Contributor
3467 Points
686 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 09, 2006 03:33 PM|LINK
I was finally able to get things working here's what I ended up doing.
Everything works now... what a trip to the dentist!
Jeff Turner
Don't forget to mark the correct answer for your
question to help out future visitors!
silver23
Member
490 Points
96 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 09, 2006 05:09 PM|LINK
ravescar
Member
40 Points
8 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 09, 2006 09:57 PM|LINK
fari enough, i am not sure why it does not install the Microsoft.Web.Extensions.Design.dll when using msiexec installer, but i will gladly provide more info if it helps.
the machine that we installed Atlas dll file to is:
windows xp pro sp1 (this is a corporate machine and we have issues installing service pack 2(something to do with Standard Operating Environment error), this is why we cannot use VWD Express)
.Net Framework 2.0
the Event viewer showed a bunch of MSI installer events such as
Product: Microsoft ASP.NET 2.0 AJAX Extensions -- Configuration completed successfully.
Product: Microsoft ASP.NET 2.0 AJAX Extensions -- Installation completed successfully.
Product: Microsoft ASP.NET 2.0 AJAX Extensions -- Configuration failed.
Product: ASP.NET 2.0 AJAX Extensions -- Removal completed successfully.
from my attempts to get stuff working and ultimately failed.
let me know if there is some other info you need.
kgohery
Member
22 Points
5 Posts
Re: New Toolkit for Beta 2 On Codeplex - Issue: No Microsoft.Web.Extensions.Design
Nov 10, 2006 08:41 AM|LINK
Hey
Yeah, this worked for me too. Thanks for the advice,
Karl
pbleic
Member
10 Points
2 Posts
Fixed problem completely
Nov 16, 2006 06:52 PM|LINK
I had the problem with No Microsoft.Web.Extensions.Design as well and fixed it completely with a few hours work. I have VWD on XP Pro and no VS.
I couldn't find an Uninstall for Atlas Extensions (even though it should have been there), so I did a search for Ajax and deleted every folder and file on my machine with Ajax ;-)
I also uninstalled the Ajax CTP (which did have an Uninstall)
I uninstalled Microsoft Web Expressions Developer (who knows, I don't use it and wanted to fix the problem).
Then, when I installed AJAX 1.0 Beta 2 again I had the file, and had an uninstall. Once I unzipped the Ajax Control Toolkit I simply used the file menu to open the website and everything worked perfectly.
Hope this helps.
mychucky
Contributor
4359 Points
3723 Posts
Re: Fixed problem completely
Dec 21, 2006 05:48 PM|LINK
I kept getting this error:
Error 1 N:\Inetpub\wwwroot\Default.master: ASP.NET runtime error: Could not load file or assembly 'Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (N:\Inetpub\wwwroot\web.config line 43) N:\Inetpub\wwwroot\Default.master 1 1 N:\Inetpub\wwwroot\
In the web server as well as the machine I used to develop the site do have all the files, System.Web.Extensions.dll, System.Web.Extensions.Design.dll, AJAXExtensionsToolbox.dll, and Microsoft.Web.Preview.dll. I also copied all of these files into my bin folder and I still received this error. It kept refferring to this line in the web.config file.
<
add assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>Any help is appreciated.
mychucky
Contributor
4359 Points
3723 Posts
Re: Fixed problem completely
Dec 21, 2006 07:16 PM|LINK