Showing posts with label upgrade. Show all posts
Showing posts with label upgrade. Show all posts

Saturday, March 24, 2012

Upgrade error: Could not load file or assembly Microsoft.Web.Extensions, Version=1.0.61025

I have upgraded from Beta 2 to RC1 and followed all of the upgrade instructions, but I'm still getting this error:

Error 26 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.

I'm aware that Microsoft.Web.Extensions is now System.Web.Extensions, but I can't find where the old reference is!!!

I have searched all the files in my project for "Microsoft.Web.Extensions" as well as the machine.config. I'm currently searching every file on my hard drive for this reference and still can't find it.

Any ideas?

Thanks,

Still looking for some help...
Do you have the ControlToolkit on your site? We had that error before we updated to the newest toolkit.

I've found you have to move the DLL files form the .NET version folder on the hard drive to the bin folder in the site otherwise they need to be in the GAC.

I'm finding other problems with it. Like [no relevant source code lines] gotta be permissions or something.

Still looking...


I have the same problem and finally found out that the reference to Microsoft.Web.Extensions is in my web.config.

Have to go through and changes all "Microsoft.Web" to "System.Web" (mainly under the<pages><controls> tag).

Upgrade from Beta

Hi ive got a server that is running ASP.NET 2.0 AJAX Extensions Beta 2,

ivebuilt a new app using the official release 1.0, when I place the new framework on the server will it cause any issues on my existing app as they will be runing side by side?

I believe that during the installation of the latest version, you will be prompted to remove the old version first. So you will need to upgrade your existing app first.

I'm not sure if copying the dlls directly from where you installed them on your machine and pasting them into the server's GAC would work or not, but it's worth a shot. Technically they're different versions and should be capable of being installed side-by-side, but the installer doesn't allow it.


There are migration guides availablehere. Side by side install is not supported. You need to upgrade to ASP.NET AJAX 1.0.

Upgrade from AJAX EXT CTP

Hi,

I currently have a web site that is developed using the ASP.NET AJAX extension released in late 2006, along with the AJAX tool kit control.

I just realised MS has release the RC1 of the AJAX extensions and BETA2 of the tool kit. I want to use the latest versions so i want to upgrade the consuming web project.

How do i go about consuming the new assemblies? Is there a step by step instruction on how to upgrade from earlier beta and CTP releases?

I am assuming there will be significant configurations required like referencing new assembles, web.config changes, tag prefixes etc

Thanks

Jim

Microsoft release Ajax 1.0 last month. You can see migration notes herehttp://ajax.asp.net/documentation/default.aspx?tabid=47

Upgrade issue - RC to full release

Hi All -

I upgraded from the RC of ASP.Net AJAX Extensions to the 1.0 full release versin.

I started by uninstalling the RC version, uninstalling the ASP.NET AJAX December Futures CTP and (here is where I probably made my mistake) removing the toolbox tabs for AJAX Extensions and the AJAX Control Toolkit.

After installing the release version of ASP.Net AJAX Extensions 1.0 and the ASP.NET AJAX January CTP I did not get the toolbox items back (for the standard items - ScriptManager - UpdatePanel - etc.). I did not even get a AJAX Extensions tab in the toolbox. I have tried running the install again and doing a repair, I tried looking for a dll to refereence when "chossing items" to add to a new tab. Nothing seems to work.

Please help

Thanks

Try adding them back manually from Tools menu, Choose Toolbox Items, Browser to Ajax/AjaxToolkit folder select .dll and select controls.


Try adding them back manually from Tools menu, Choose Toolbox Items, Browser to Ajax/AjaxToolkit folder select .dll and select controls.

Alos

Try adding them back manually from Tools menu, Choose Toolbox Items, Browser to Ajax/AjaxToolkit folder select .dll and select controls.

Also

Try adding them back manually from Tools menu, Choose Toolbox Items, Browser to Ajax/AjaxToolkit folder select .dll and select controls.

Also follow

Thanks Nilesh -

I get the same interface as I do when right clicking on the tab - I select the AJAXExtensionsToolBox.dll and an error message pops up - "There are no components in AJAXExtensionsToolBox.dll that can be placed on the toolbox".

This is not the AJAX Toolkit I am tryng to recover the toolbox items for - it is the basic AJAX tools...

NileshDesh:

Try adding them back manually from Tools menu, Choose Toolbox Items, Browser to Ajax/AjaxToolkit folder select .dll and select controls.

Also follow

Upgrade issue - Please Help

Hi All -

I still have not resolved this issue from a previous post - any help appreciated.

I upgraded from the RC of ASP.Net AJAX Extensions to the 1.0 full release versin.

I started by uninstalling the RC version, uninstalling the ASP.NET AJAX December Futures CTP and (here is where I probably made my mistake) removing the toolbox tabs for AJAX Extensions and the AJAX Control Toolkit.

After installing the release version of ASP.Net AJAX Extensions 1.0 and the ASP.NET AJAX January CTP I did not get the toolbox items back (for the standard items - ScriptManager - UpdatePanel - etc.). I did not even get a AJAX Extensions tab in the toolbox. I have tried running the install again and doing a repair, I tried looking for a dll to refereence when "chossing items" to add to a new tab. Nothing seems to work.

This is *NOT* the ASP.Net Ajax Toolkit that I am refering to - but the main ASP.NET Framework install and the main tools like ScriptManager and UpdatePanel.

Thanks...

To get the main controls into your toolbox, and into a tab, you need to first right-click inside a blank area of your toolbox and choose 'Add Tab', which you can then rename. Next, make sure that tab is extended/open, then right click in a blank area under the tab and click 'choose items'. Under the .NET Framework Components tab, click on the 'Assembly Name' column heading to sort by assembly names. Scroll down to the first entry for the "System.Web.Extensions" assembly, then place a checkmark next to each control from that assembly. Select 'OK' and you should be all set.

If you don't see them in the component box, try doing the above in a project that currently has System.Web.Extensions as a reference.


I am not finding System.Web.Extensions which is weird because I can still actually add the controls to a page by clicking the source tab and then just putting the HTML tags in like <asp:ScriptManager></asp:ScriptManager> .This works but no matter what I do I cannot get the items into the toolbox.

ps2goat:

To get the main controls into your toolbox, and into a tab, you need to first right-click inside a blank area of your toolbox and choose 'Add Tab', which you can then rename. Next, make sure that tab is extended/open, then right click in a blank area under the tab and click 'choose items'. Under the .NET Framework Components tab, click on the 'Assembly Name' column heading to sort by assembly names. Scroll down to the first entry for the "System.Web.Extensions" assembly, then place a checkmark next to each control from that assembly. Select 'OK' and you should be all set.

If you don't see them in the component box, try doing the above in a project that currently has System.Web.Extensions as a reference.


James Evans:

I am not finding System.Web.Extensions which is weird because I can still actually add the controls to a page by clicking the source tab and then just putting the HTML tags in like <asp:ScriptManager></asp:ScriptManager> .This works but no matter what I do I cannot get the items into the toolbox.

Check your global assembly cache to make sure anything with Microsoft.web has been uninstalled. (you may need to uninstall January CTP for this... reinstall it later). Windows directory/assembly/. (In my case, after installing service pack 1, the older versions of AJAX were no longer displayed in the control panel for removal).

To add the System.Web.Extensions dll to a project, you'll need to navigate to where the dll was installed. by default, this is %Program files%\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025\. (You may see remnants from Microsoft.Web dlls in here, too).

You should then be able to add the controls to the toolbox as described in the previous post.

Upgrade January project to March project

Can someone tell me how I can upgrade an existing January release project to the new March release project?

Thanks.

1. Remove the old ScriptLibrary folder from your app
2. Replace Microsoft.Web.Atlas.dll with the new DLL
3. Update your web.config based on the new web.config that comes with the March CTP

Thanks,

Eilon

Upgrade to Ajax extensions 1.0 problem

I'm having a problem with upgrading my website to the 1.0 release of Ajax. I've tried to remove all traces of Microsoft.Web and replaced it with System.Web but somewhere there is a reference to Microsoft.Web and I can't find it. I've searched the entire solution dir and its not mentioned anywhere in there. I've searched the registry and its in there a few times but only in reference to my searches or old projects. I know that my machine is configured properly because I can add a new Ajax enabled website to my solution and the works fine. Below is the error I'm getting and my Web.config. There seems to be a "post-policy reference" to Microsoft.Web.Extensions but I haven't the faintest idea where that is coming from. Please help!

Server Error in '/DanTest' Application.
------------------------

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.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: 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.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.

=== Pre-bind state information ===
LOG: User = TBS-7AF178B6C10\ASPNET
LOG: DisplayName = Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
(Fully-specified)
LOG: Appbase = file:///C:/STProjects/EA/Mozart/Sources/Mozart_DMZ/Mozart.Website/
LOG: Initial PrivatePath = C:\STProjects\EA\Mozart\Sources\Mozart_DMZ\Mozart.Website\bin
Calling assembly : (Unknown).
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\STProjects\EA\Mozart\Sources\Mozart_DMZ\Mozart.Website\web.config
LOG: Using host configuration file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet.config
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Post-policy reference: Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/dantest/bc4e166c/738e1bd2/Microsoft.Web.Extensions.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/dantest/bc4e166c/738e1bd2/Microsoft.Web.Extensions/Microsoft.Web.Extensions.DLL.
LOG: Attempting download of new URL file:///C:/STProjects/EA/Mozart/Sources/Mozart_DMZ/Mozart.Website/bin/Microsoft.Web.Extensions.DLL.
LOG: Attempting download of new URL file:///C:/STProjects/EA/Mozart/Sources/Mozart_DMZ/Mozart.Website/bin/Microsoft.Web.Extensions/Microsoft.Web.Extensions.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/dantest/bc4e166c/738e1bd2/Microsoft.Web.Extensions.EXE.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/dantest/bc4e166c/738e1bd2/Microsoft.Web.Extensions/Microsoft.Web.Extensions.EXE.
LOG: Attempting download of new URL file:///C:/STProjects/EA/Mozart/Sources/Mozart_DMZ/Mozart.Website/bin/Microsoft.Web.Extensions.EXE.
LOG: Attempting download of new URL file:///C:/STProjects/EA/Mozart/Sources/Mozart_DMZ/Mozart.Website/bin/Microsoft.Web.Extensions/Microsoft.Web.Extensions.EXE.

Stack Trace:

[FileNotFoundException: 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.]
System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0
System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +211
System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +141
System.Reflection.Assembly.Load(String assemblyString) +25
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +32

[ConfigurationErrorsException: 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.]
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +596
System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +70
System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +177
System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +180
System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) +347
System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) +125
System.Web.Compilation.BuildManager.CompileCodeDirectories() +525
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +448

[HttpException (0x80004005): 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.]
System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +57
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +612
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters) +456

[HttpException (0x80004005): 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.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3434959
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +252

 
Here is my web.config:
<?xml version="1.0"?>
<configuration>
<configSections>
<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>
<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
</sectionGroup>
</sectionGroup>
</sectionGroup>
</configSections>
<connectionStrings configSource=".\\App_Data\\EnvironmentSettings.xml"/>
<!-- The following is need so that an unauthenticate user has access to the AJAX script files. -->
<location path="ScriptResource.axd">
<system.web>
<authorization>
<allow users="*"/>
</authorization>
</system.web>
</location
<system.web>
<authorization>
<deny users="?"/>
</authorization>
<customErrors mode="Off"/>
<authentication mode="Forms">
<forms name="Mozart" defaultUrl="/Default2.aspx" timeout="1440"/>
</authentication>
<pages>
<controls>
<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</controls>
</pages>
<compilation debug="true">
<assemblies>
<add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.ServiceProcess, 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="System.Web.RegularExpressions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Web.Extensions.Design, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Drawing.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies>
</compilation>
<httpHandlers>
<remove verb="*" path="*.asmx"/>
<add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false"/>
</httpHandlers>
<httpModules>
<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</httpModules>
<!-- ___________________________ Profiles ___________________________ -->
<profile defaultProvider="MozartProfileSqlProvider">
<providers>
<clear/>
<add name="MozartProfileSqlProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="EnvironmentSettings.Mozart" applicationName="Mozart"/>
</providers>
<properties>
<add name="OrganizationId"/>
<add name="BackgroundColor"/>
<group name="PhoneNumbers">
<add name="Home"/>
<add name="Mobile"/>
<add name="Business"/>
</group>
</properties>
</profile>
<!-- ___________________________ Membership ___________________________ -->
<membership defaultProvider="MozartMembershipSqlProvider">
<providers>
<add name="MozartMembershipSqlProvider" connectionStringName="EnvironmentSettings.Mozart" applicationName="Mozart" type="System.Web.Security.SqlMembershipProvider" requiresUniqueEmail="false" minRequiredPasswordLength="5" minRequiredNonalphanumericCharacters="0"/>
</providers>
</membership>
<!-- ___________________________ Roles ___________________________ -->
<roleManager enabled="true" defaultProvider="MozartAspNetSqlRoleProvider">
<providers>
<add applicationName="Mozart" connectionStringName="EnvironmentSettings.Mozart" name="MozartAspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
</providers>
</roleManager>
</system.web>
<!-- ___________________________ SiteMap ___________________________ -->
<location allowOverride="false">
<system.web>
<siteMap defaultProvider="MozartSiteMapProvider" enabled="true">
<providers>
<add name="MozartSiteMapProvider" description="Mozart SiteMap provider" type="System.Web.XmlSiteMapProvider" securityTrimmingEnabled="true" siteMapFile="Web.sitemap"/>
</providers>
</siteMap>
</system.web>
</location>
<system.web.extensions>
<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 ASP.NET AJAX applications, you need to add each property name to the readAccessProperties and
writeAccessProperties attributes. -->
<!--
<profileService enabled="true"
readAccessProperties="propertyname1,propertyname2"
writeAccessProperties="propertyname1,propertyname2" />
-->
</webServices>
<!--
<scriptResourceHandler enableCompression="true" enableCaching="true" />
-->
</scripting>
</system.web.extensions>
<system.webServer>
<validation validateIntegratedModeConfiguration="false"/>
<modules>
<add name="ScriptModule" preCondition="integratedMode" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</modules>
<handlers>
<remove name="WebServiceHandlerFactory-Integrated"/>
<add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</handlers>
</system.webServer>
</configuration
------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210
I fixed it. I had a web.config in the root of my local webserver (C:\inetpub\wwwroot) that was messing it up when I launched from VS. If I set the project to the default server it worked fine. I deleted the web.config in the root and now both work fine.

Upgrade to Beta 1 = New Rating control error

I installed the latest framework and toolkit.

My project was working fine with a wizard control that contained rating controls. I've taken the rating controls out of the wizard template and put them in their own update panel and still receive the error. It's a very strange behavior. If I make a new page and do everything, the rating control works fine. I'm using the latest control and did all the changes required to use the new Beta. After the install, I keep receiving this error when loading the page:

System.InvalidOperationException was unhandled by user code
Message="The TargetControlID of '_RatingExtender' is not valid. The value cannot be null or empty."
Source="Microsoft.Web.Extensions"
StackTrace:
at Microsoft.Web.UI.ExtenderControl.RegisterWithScriptManager()
at Microsoft.Web.UI.ExtenderControl.OnInit(EventArgs e)
at AjaxControlToolkit.ExtenderControlBase.OnInit(EventArgs e) in C:\Program Files\Microsoft ASP.NET\AjaxControlToolkit\AjaxControlToolkit\ExtenderBase\ExtenderControlBase.cs:line 338
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at System.Web.UI.ControlCollection.Add(Control child)
at Microsoft.Web.UI.UpdatePanel.SingleChildControlCollection.AddSingleChild(Control child)
at Microsoft.Web.UI.UpdatePanel.AddContentTemplateContainer()
at Microsoft.Web.UI.UpdatePanel.CreateContents(Boolean recreate)
at Microsoft.Web.UI.UpdatePanel.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Thanks

Anyone ? Can you please take a look? I believe others are experiencing something similar with the mentioned TargetControlID.

Thanks


When the project breaks, it breaks at the bold:

/// <summary>
/// On Init we load target properties values and process databinding handlers.
/// </summary>
/// <param name="e"></param>
protected override void OnInit(EventArgs e)
{
if (EnableClientState)
{
CreateClientStateField();
}
// EnsureProfileScriptService(ScriptManager.GetCurrent(Page), true);
Page.PreLoad += new EventHandler(Page_PreLoad);
base.OnInit(e);
}


Please reply with acomplete, self-contained sample page that demonstrates the problem. Thank you!

In my case the problem occures when I specify the rating control in the skin file.

Skinfile:

<

ajaxToolkit:Ratingrunat="server"StarCssClass="ratingStar"WaitingStarCssClass="savedRatingStar"FilledStarCssClass="filledRatingStar"EmptyStarCssClass="emptyRatingStar"/>
Good to know! Do you have a complete, self-contained sample we can play with?

Just add the following 2 lines in the Default.skin file of the Ajax Control Toolkit SampleWebSite:

<%@.RegisterAssembly="AjaxControlToolkit"Namespace="AjaxControlToolkit"TagPrefix="ajaxToolkit" %>
<ajaxToolkit:Ratingrunat="server"StarCssClass="ratingStar"WaitingStarCssClass="savedRatingStar"FilledStarCssClass="filledRatingStar"EmptyStarCssClass="emptyRatingStar"/>

Then try to open the Rating sample of the SampleWebSite.


The SampleWebSite doesn't have a Default.skin file - might there be something else going on here that's causing issues?

upgrade to the new release of control toolkit provides versioning trouble

Hi,

I just copied and pasted the new dll of the control toolkit over the old ones. Then i changed the app.config to reflect the new version number :

<addtagPrefix="ajaxToolkit"namespace="AjaxControlToolkit"assembly="AjaxControlToolkit, Version=1.0.10606.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e"/>

I also removed all the icons from the toolbox and added them in again.

when i drag an item from the toolbox onto my form, it gives it the tag prefix of cc1 instead of ajaxToolkit.

like

<cc1:TabPanelID="TabPanel1"runat="server">

</cc1:TabPanel>

What is it that i am missing?

Thanks!

It is perfectly normal.

Refer to the following post for more details

http://forums.asp.net/p/1117736/1736819.aspx#1736819


Thanks for the reply and the link. According to the book that you link to, the developers need to add[assembly:TagPrefix("AjaxControlToolkit ", " ajaxToolkit ")] to theAssemblyInfo.cs file for this problem to go away.


First of all, it is not a problem. You don't need to worry about the tag prefix used by the controls.

The tag prefix is decided by the developer of the control. He makes the entry into the AssemblyInfo.cs of the control.

Upgrade woes

I've installed the latest AJAX 1.0 package, but when I try to compile my project I get:

Error 102 C:\Documents and Settings\Chris\My Documents\My Webs\Tasks\Default.aspx: 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. C:\Documents and Settings\Chris\My Documents\My Webs\Tasks\Default.aspx 1 1 C:\...\Tasks\

I do a find in solution for 'Microsoft.Web.Extensions', and there are no results. What is trying to load this .dll?

Ok, if you have an older version and you upgraded, you need also to upgrade your web.config

This link will show you how:http://alpascual.com/blog/al/archive/2007/02/05/Manually-upgrading-any-project-to-ASP.NET-2.0-AJAX-1.0.aspx

Hope this helps

Upgrading Ajax Control Toolkit

Is there a faq on how to upgrade an existing app to a newer version of the control toolkit? What needs to be done etc?

Replace the old toolkit dll reference in your project(s) to the dll from the current release.


Seethis forum post for more details.

Upgrading ASP.NET 2.0 projects to Atlas

How do you upgrade an existing ASP.NET 2.0 project to Atlas? I already install the Atlas April 2006 CTP. I can create Atlas websites in VS 2005 but I want to upgrade some of the projects I have to Atlas.

hello.

well, you need to put the atlas dll on the bin folder, copy some entries from the default atlas web.config to your app's config and, if you're using bridges, add a new extension to iis.


bass_player...

Try these instructions on my blog -http://codebetter.com/blogs/jay.kimble/archive/2006/05/19/144952.aspx

I think they will help you out considerably.

Jay


bass_player...

Try these instructions on my blog -http://codebetter.com/blogs/jay.kimble/archive/2006/05/19/144952.aspx

I think they will help you out considerably.

Jay


Thanks a lot Jay, I really appreciate this. I just need to try it out. Will give you some updates.

Upgrading Extender control from Atlas to ASP.NET AJAX

Hi,

I have an extender control written in atlas. I want to upgrade it to asp.net ajax.

Its so sad that there are no documentation for upgrading an extender control.

My extender control is as follows.

publicclassMyExtender : ExtenderControl<MyTargetProperties>

{

public MyExtender()

{

}

publicstring ControlID

{

get

{

return (string)ViewState["ControlID"] ??"";

}

set

{

ViewState["ControlID"] =value;

}

}

protectedoverridevoid OnInit(EventArgs e)

{

// Init code

base.OnInit(e);

}

protectedoverridevoid OnLoad(EventArgs e)

{

base.OnLoad(e);

}

protectedoverridevoid OnPreRender(EventArgs e)

{

base.OnPreRender(e);

}

protectedoverridevoid RenderScript(Microsoft.Web.Script.ScriptTextWriter writer,Control targetControl)

{

// write the script here

}

}

publicclassMyTargetProperties : TargetControlProperties

{

protectedoverridebool IsEmpty

{

get {returnfalse; }

}

}

Can somebody suggest what I need to do ?

The moment I remove the Microsoft.Web.UI namespace, I get plenty of errors.

Thanks

Hi,

Maybe it's not too hard to start with a new control based on the doc, and migrate your code:

Adding Client Behaviors to Web Server Controls by Using ASP.NET AJAX Extensions

or

Adding Client Capabilities to a Web Server Control by Using ASP.NET AJAX Extensions


hello.

well, several things have change since then but i'll try to recall what yoyu need to do. the first thing is to drop the targetcontrolproperties since they are no longer needed.

the second thing you need to know is that the client behavior object (JS) is introduced in the page through what is know as a ScriptDescriptor object. currently,you have 2 options: ScriptBehaviorDescriptor and ScriptControlDescriptor (it all depends on what you're developing: behaviors or client controls). Besides one of these objects, you'll also need a scriptreference to indicate the client files that must be loaded. what you can't forget is to:

1. during prerender, call registerextendercontrol method

2. during the render method, you must call the registersccriptdescriptors

do notice that if you're extending the extendercontrol class then you don't need to worry about this: just override the abstract getscriptdescriptors and getscriptreferences methods

i still think that the easiest way to understand what's going on is to use reflector and take a look the code you have in the current version of the platform...

Upgrading from Beta 2 to 1.0 in production server

Hi there! I'm going to upgrade MS Ajax as subject. I read somewhere else I should restart IIS to make it use the new version. How can I do it without restarting the server? Any other things I should have in mind while performing the upgrade?

Thanks,

-Benton

Hi benton,

Restart IIS --> Open --> run --> iisrestart

Regards,

Upgrading June CTP to July CTP

What is the best way to do this, uninstall the June CTP then run the installer for the July CTP, or run the July CTP msi and it will upgrade an older version?

hello.

i think that the correct behavior is uninstall and then install the new version.

Upgrading the AJAX Control Toolkit?

If I have a directory called AJAXCTPEnabledWebsite1 in my VS websites folder, how do I upgrade that to the release version? I guess I'm not sure what the difference is between AJAX 1.0 and the AJAX Control Toolkit. If I have the AJAX Control Toolkit, does that mean I already have AJAX (pre 1.0 in my case) installed?

I just need to get upgraded to the release version(s) and need a little direction. Any help will be greatly appreciated. Which of these do I need:

http://ajax.asp.net/downloads/default.aspx?tabid=47

You needboth, the RTM version of ASP.Net AJAX and the latest version of the toolkit. You will need to recompile your project against the latest bits and check for any issues. You can find toolkit breaking changes information under thearchived releases section of the toolkit and ASP.Net AJAX breaking changeshere.

The latest version is v1.0.10301.0. Download that release (its the latest one), get the zip files that includes all the files. In the Sample Websites/Bin you will see "AjaxControlToolkit.dll". Thats the dll you need to import in to your VS Toolkit.


kirtid:

You needboth, the RTM version of ASP.Net AJAX and the latest version of the toolkit. You will need to recompile your project against the latest bits and check for any issues. You can find toolkit breaking changes information under thearchived releases section of the toolkit and ASP.Net AJAX breaking changeshere.

So is the 'beta' of the control toolkit the ASP.NET AJAX RC or the ATLAS version? I found the migration docs, but they are different based on which version you have. As I said, I have the 'beta', but I'm not sure if that is the same as the AJAC RC or the ATLAS version. I believe it should be the AJAX RC, but I want to confirm before I start uninstalling/installing. In the link below, it mentions 'beta' in the sentance above two possible documents, but the links and info about the actual links don't label either one as migration from the 'beta'.

Specifically, on this page, do I use the first or second migration document if I have the Control Toolkit 'beta'?: http://ajax.asp.net/documentation/default.aspx?tabid=47

Thanks for the info.


The toolkit is built on top of the ASP.Net AJAX platform. They are two separate entities. ASP.Net AJAX RTM is what the latest version of the toolkit uses. You should always use the latest version of the toolkit which is what we support. I pointed you to the archived releases in case you wanted to check out any older breaking changes. You should uninstall all older versions of ASP.Net AJAX before installing the RTM build, then download the latest version of the toolkit and compile your project against these new dlls.


Ahh, OK, now I see, that makes sense. Thanks!

upgrading to ajax.net from Atlas 2.0

Hi, after searching around a bit on this forum I'm not really finding info on how to upgrade to the latest ajax.net from an old Atlas 2.0 project I have.

I have a working project that is Atlas 2.0.5xxx... Is there special instructions on upgrading to ajax.net 1.0? or should I just download it and follow normal install instructions?

Thanks very much.

-JBD

Hi,JBD

Check this articlehttp://groups.google.mu/group/ajaxpro/msg/828724afed7d8132

Let me know if you need more info.

Thanks

NOTE:This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.

Upgrading to CTP / ASP.net Ajax

hey guy,

finally i decided to upgrade my ajax framework to the most recent one and i notice some errors which i havn't recieve beofer the upgrade. can someone give a hand here? i really need to resolve those problems ASAP.

this first problem that i'm getting is document.body is null or not an object (the debugger stops in this line):

AjaxControlToolkit._CommonToolkitScripts = function() { /// /// The _CommonToolkitScripts class contains functionality utilized across a number /// of controls (but not universally) /// // Populate the borderThicknesses lookup table this._borderThicknesses = { }; var div0 = document.createElement('div'); var div1 = document.createElement('div'); div0.style.visibility = 'hidden'; div0.style.position = 'absolute'; div0.style.fontSize = '1px'; div1.style.height = '0px'; div1.style.overflow = 'hidden';document.body.appendChild(div0).appendChild(div1);

and the second one is commontoolscripts is null or not an object:

AjaxControlToolkit.ModalPopupBehavior.callBaseMethod(this, 'initialize'); this._foregroundElement = $get(this._PopupControlID); this._backgroundElement = document.createElement('div'); this._backgroundElement.style.display = 'none'; this._backgroundElement.style.position = 'absolute'; // Want zIndex to big enough that the background sits above everything else // CSS 2.1 defines no bounds for the type, so pick arbitrarily this._backgroundElement.style.zIndex = 10000; if (this._BackgroundCssClass) { this._backgroundElement.className = this._BackgroundCssClass; } this._foregroundElement.parentNode.appendChild(this._backgroundElement); this._foregroundElement.style.display = 'none'; this._foregroundElement.style.position = 'absolute'; this._foregroundElement.style.zIndex =CommonToolkitScripts.getCurrentStyle(this._backgroundElement, 'zIndex', this._backgroundElement.style.zIndex) + 1;

thanks,

ori

Did you move to AJAX RC ? Did you move from Beta 2 or CTP ? Use following document

CTP to RC

http://ajax.asp.net/files/Migration_Guide_CTP_to_RC.aspx

Beta 2 to RC

http://ajax.asp.net/files/Migration_Guide_Beta2_to_RC.aspx