Versions Compared

Old Version 2

changes.mady.by.user Noreen Dertinger

Saved on

compared with

New Version Current

changes.mady.by.user Noreen Dertinger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • after upgrading AJAX Control Toolkit from 4x to 7 the error message below was displayed on clicking Ènglish or French buttons the message below was displayed.

    • Solved by temporarily changing the id (html1) to HTML1, that is changed and back again:
      Steps

      • Changed Line 4: <html id="Html1" runat="server">

      • to Line 4: <html id="HTML1" runat="server">

        • Selected “clean” and “rebuild” and “rebuild.

        • then changed line 4 back to the original

      • Line 4: <html id="Html1" runat="server">

...

Server Error in '/' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: The base class includes the field 'Html1', but its type (System.Web.UI.HtmlControls.HtmlGenericControl) is not compatible with the type of control (System.Web.UI.HtmlControls.HtmlElement).

Source Error:

Line 2:
Line 3: <!DOCTYPE html >
Line 4: <html id="Html1" runat="server">
Line 5: <head id="Head1" runat="server">
Line 6: <title></title>

Source File: /Site.Master Line: 4

Version Information: Microsoft .NET Framework Version:4.0.30319; http://ASP.NET Version:4.8.9282.0

BC30002 Type 'Global.AjaxControlToolkit.ToolkitScriptManager' is not defined

This error was reported for 19 designer files when I upgraded AjaxControlToolkit to the latest version (20.x)

the ToolkitScriptManager was removed from AjaxControlToolkit in about v. 15 as it is replaced by the standard asp.net script manager.


For example, CAPMS-SGPMC C:\Users\dertinn\source\repos\CAPMS-SGPMC2\Source\CAPMS-SGPMC\a_e.aspx.designer.vb 23

Originally I tried doing a rename of all the references to ToolkitScriptManager in the aspx files.
This did not resolve the error reported for the designer file, such as the one above and triggered additional errors as well.

We cannot edit the designer files because they are “generated”

The solution below eliminated the error and triggered the regeneration of the associated designer file(s).

Currently, I did it one by one, will investigate if there is an easier way later.

This is what works: Issue regarding ToolkitScriptManager - Microsoft Q&A