same problem, i do not use VS here at all and there is no Microsoft.Web.Extensions.Design.dll in

C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025 at all after installed beta 2 from

Jody said

        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

 - I don't these entries !!!

    (I have installed the 2 MSI files - running VISTA) 

Any further ideas
 

 

You'll probably need to add a reg setting:

 

 In HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\AssemblyFolders\ASP.NET AJAX 1.0.61025

 

change the default value (or add it)  c:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025

 

Note in the example above c is my root - if you boot to a d or other drive - change the letter - can not use variables to denote it...

 

That should after a reboot - allow you to see the assemblies in the .Net tab
 

ravescar:

same problem, i do not use VS here at all and there is no Microsoft.Web.Extensions.Design.dll in

C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025 at all after installed beta 2 from

 

Is c: your boot partition of the system?  If you are running a dual boot system it will be in the boot drives program files.

 

The installer does drop the bits down unless there is a error with the install... in which case there should be something in your Event Log under Applications...

 

 

never mind, i fixed the problem by manually extract the Microsoft.Web.Extensions.Design.dll using a tool from this link

http://blogs.pingpoet.com/overflow/archive/2005/11/16/14995.aspx

then dump the dll file into /bin directory for the web application, work like a charm.
 

jodywbcb:

ravescar:

same problem, i do not use VS here at all and there is no Microsoft.Web.Extensions.Design.dll in

C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025 at all after installed beta 2 from

 

Is c: your boot partition of the system?  If you are running a dual boot system it will be in the boot drives program files.

 

The installer does drop the bits down unless there is a error with the install... in which case there should be something in your Event Log under Applications...

 

 

 

yeah, that pc only has one hard drive and one partition so that can't be the problem. there is no simpler scenario.

i checked the timestamp for the dll files on that directory and i am sure they are updated.

 

i think the installer somehow decided my pc does not need Microsoft.Web.Extensions.Design.dll :D

anyhow, the problem is gone for me, hope it helps for you.
 

aa0606:

So I have a beta 2 site that works perfectly on my local dev box.  When I went to deploy the site to my server (w/o VS installed - the server also previously had beta 1 installed) and was receiving the Microsoft.Web.Extensions.Design.dll error message.  I copied the Microsoft.Web.Extensions.Design.dll to the /bin folder of my site on the server, and now I am receiving the following error messge:

Parser Error Message: Unknown server tag 'asp:UpdateProgress'

So just for fun, I removed the UpdateProgress controls from my page.  After that, the page loads, however, none of the Toolkit controls (i.e. dropshadow, popupmenu) are working on my page.

I have tried un-installing and re-installing the beta 2 core package and the november ctp, but that changed nothing.

Thanks in advance,
Andy

 

Andy - you may try to change the prefix in the web.config to make it say ajax and not asp for the ajax stuff ...  I do that as there was the issue with the last Beta 1.

 

Secondly - you may want to reverse engineer your web.config...  although I don't recommend using the toolkit as the model as it leaves out the core config entries to make ajax work (even with the toolkit examples which is why I ended up spending so much time to to debug why nothing was working... here is my reworked config for the toolkit...

 

to make it work with the toolkit - however, change the <controls> section to asp and not ajax - however since I use this as the template for my projects I changed it to ajax...

 

 

<configuration>
	<configSections>
		<sectionGroup name="microsoft.web" type="Microsoft.Web.Configuration.MicrosoftWebSectionGroup, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
			<sectionGroup name="scripting" type="Microsoft.Web.Configuration.ScriptingSectionGroup, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
				<sectionGroup name="webServices" type="Microsoft.Web.Configuration.ScriptingWebServicesSectionGroup, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
					<section name="jsonSerialization" type="Microsoft.Web.Configuration.ScriptingJsonSerializationSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>
					<section name="profileService" type="Microsoft.Web.Configuration.ScriptingProfileServiceSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>
					<section name="authenticationService" type="Microsoft.Web.Configuration.ScriptingAuthenticationServiceSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>
				</sectionGroup>
			</sectionGroup>
		</sectionGroup>
	</configSections>
	<system.web>
		<trace enabled="false"/>
		<trust level="Medium"/>
		<pages>
			<controls>
				

					<add tagPrefix="ajax" namespace="Microsoft.Web.UI" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
					<add tagPrefix="ajax" namespace="Microsoft.Web.UI.Controls" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
					<add tagPrefix="ajax" namespace="Microsoft.Web.Preview.UI" assembly="Microsoft.Web.Preview"/>
					<add tagPrefix="ajax" namespace="Microsoft.Web.Preview.UI.Controls" assembly="Microsoft.Web.Preview"/>
				
			</controls>
			<tagMapping>
				<add tagType="System.Web.UI.WebControls.CompareValidator" mappedTagType="Microsoft.Web.UI.Compatibility.CompareValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagType="System.Web.UI.WebControls.CustomValidator" mappedTagType="Microsoft.Web.UI.Compatibility.CustomValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagType="System.Web.UI.WebControls.RangeValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RangeValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagType="System.Web.UI.WebControls.RegularExpressionValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RegularExpressionValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagType="System.Web.UI.WebControls.RequiredFieldValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RequiredFieldValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add tagType="System.Web.UI.WebControls.ValidationSummary" mappedTagType="Microsoft.Web.UI.Compatibility.ValidationSummary, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
			</tagMapping>
		</pages>
		<!-- 
          Set compilation debug="true" to insert debugging 
          symbols into the compiled page. Because this 
          affects performance, set this value to true only 
          during development.
    -->
		<compilation debug="false">
			<assemblies>
				<add assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
				<add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
				<add assembly="Microsoft.Web.Extensions.Design, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></assemblies>
		</compilation>
		<httpHandlers>
			<remove verb="*" path="*.asmx"/>
			<add verb="*" path="*.asmx" validate="false" type="Microsoft.Web.Script.Services.ScriptHandlerFactory, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
			<add verb="GET" 
			   path="ScriptResource.axd" 
			   type="Microsoft.Web.Handlers.ScriptResourceHandler" 
			   validate="false"/>
		</httpHandlers>
		<httpModules>
			<add name="WebResourceCompression" type="Microsoft.Web.Handlers.WebResourceCompressionModule, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
			<add name="ScriptModule" type="Microsoft.Web.UI.ScriptModule, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
		
		</httpModules>
		<siteMap defaultProvider="SamplesSiteMap">
			<providers>
				<add name="SamplesSiteMap" type="System.Web.XmlSiteMapProvider" siteMapFile="~/Samples.sitemap"/>
				<add name="WalkthroughsSiteMap" type="System.Web.XmlSiteMapProvider" siteMapFile="~/Walkthroughs.sitemap"/>
			</providers>
		</siteMap>
	</system.web>
	<microsoft.web>
		<scripting>
			<webServices>
				<!-- Uncomment this line to customize maxJsonLength and add a custom converter -->
				<!--
      <jsonSerialization maxJsonLength="500">
        <converters>
          <add name="ConvertMe" type="Acme.SubAcme.ConvertMeTypeConverter"/>
        </converters>
      </jsonSerialization>
      -->
				<!-- Uncomment this line to enable the authentication service. Include requireSSL="true" if appropriate. -->
				<!--  
        <authenticationService enabled="true" requireSSL = "true|false"/>
      -->
				<!-- Uncomment these lines to enable the profile service. To allow profile properties to be retrieved 
           and modified in Atlas applications, you need to add each property name to the setProperties and 
           getProperties attributes. -->
				<!--  
      <profileService enabled="true" 
                      setProperties="propertyname1,propertyname2" 
                      getProperties="propertyname1,propertyname2" />
      -->
			</webServices>
		</scripting>
	</microsoft.web>
	<system.webServer>
		<validation validateIntegratedModeConfiguration="false"/>
		<modules>
			<add name="ScriptModule" preCondition="integratedMode" type="Microsoft.Web.UI.ScriptModule, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
		</modules>
		<handlers>
			<remove name="WebServiceHandlerFactory-ISAPI-2.0"/>
			<add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="Microsoft.Web.Script.Services.ScriptHandlerFactory, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
		</handlers>
	</system.webServer>
</configuration>

  

 

 

Hope that helps... 

ravescar:

jodywbcb:

ravescar:

same problem, i do not use VS here at all and there is no Microsoft.Web.Extensions.Design.dll in

C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025 at all after installed beta 2 from

 

Is c: your boot partition of the system?  If you are running a dual boot system it will be in the boot drives program files.

 

The installer does drop the bits down unless there is a error with the install... in which case there should be something in your Event Log under Applications...

 

 

 

yeah, that pc only has one hard drive and one partition so that can't be the problem. there is no simpler scenario.

i checked the timestamp for the dll files on that directory and i am sure they are updated.

 

i think the installer somehow decided my pc does not need Microsoft.Web.Extensions.Design.dll :D

anyhow, the problem is gone for me, hope it helps for you.
 

 

I am responding merely becaue this is a ISSUE... do you perhaps have third party controls such as spybot. antivirus etc.. that would prevent this.. you event log should annotate install issues..if you are getting the extension dll but not hte designer.dll...seomthing here is wrong and MSFT needs to be aware of the issue... so if you could provide a bit more at least in event logs .. would be helpful...I am not a rep for MSFT but very intune to how they handle installation etc...  I f we can get a bit more info whee it is failing for you,.. then we can direct future install considerations..........

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

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

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

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.

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.

jimmy0x52 :

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!

 

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?