locked
Unknown server tag 'ajax:calendarextender' RRS feed

  • Question

  • User-197858694 posted

    Hello-

     I am using Visual Web Developer 2008 Express Edition, and have had no trouble using AJAX, but when I try to use anything from the AJAX Control Toolkit, it doesn't work. I have followed all the steps I found on this site and others, and although I can get the Sample Web Site to open and run, it doesn't work when I try to use one on my own existing site.

     
    I have this at the top of the page:

    <%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="ajax" %>

    AjaxControlToolkit.dll and AjaxControlToolkit.pdb, as well as all the folders like "ar," "cs," etc. are in my Bin folder. I have also tried replacing my web.config file with the one that comes with the sample web site, but no luck there.

    Here is the error:

    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: Unknown server tag 'ajax:calendarextender'.

    Source Error:

    Line 228:                    <asp:TextBox ID="txtCOStartDate" runat="server" />
    Line 229: <asp:ImageButton runat="server" ID="btnCOStartCal" ImageUrl="images/icon_calendar.png" />
    Line 230: <ajax:calendarextender runat="server" ID="calStart" TargetControlID="txtCOStartDate"
    Line 231: PopupButtonID="btnCOStartCal" /><br />
    Line 232: <label for="calEnd" title="Ending Date">End Date</label>

    Source File: /Laptops/Laptops.aspx    Line: 230
     

    Any ideas? Let me know if there's more info I can provide.

    Monday, January 7, 2008 8:30 PM

Answers

  • User-1281179732 posted

    boy first remove any reference to your AJAX  dll then add reference to file in bin folder,

    remove assembly (Controls toolkit) from GAC.

    Register assembly in web.config file. if this isn't work send me your project.
     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, January 8, 2008 4:28 AM

All replies

  • User-1281179732 posted

    boy first remove any reference to your AJAX  dll then add reference to file in bin folder,

    remove assembly (Controls toolkit) from GAC.

    Register assembly in web.config file. if this isn't work send me your project.
     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, January 8, 2008 4:28 AM
  • User-1684099974 posted

    Also, make sure you have the correct version of the Toolkit.  There is now one version for VS 2005 and one for VS 2008.

    Tuesday, January 8, 2008 10:19 AM
  • User-197858694 posted

    boy first remove any reference to your AJAX  dll then add reference to file in bin folder,

    remove assembly (Controls toolkit) from GAC.

    Register assembly in web.config file. if this isn't work send me your project.

     

     Can you go into a little more detail by chance? I'm afraid I'm learning as I'm going, and I didn't really know anything about the GAC until now. I researched it, found gacutil.exe on my system, but apparently it wasn't installed in the first place (I used "gacutil /l AjaxControlToolkit" and it found nothing). I used the utility to add it, and figured out how to register the assembly in web.config:

    <add assembly="<span" class="st"><add assembly="AjaxControlToolkit, Version=3.0.11119.25533, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e, processorArchitecture=MSIL"/></add>

     It does actually work now, on localhost at least, but I was reading up some more on gacutil.exe, and it said installing an assembly that way was a bad idea:

     

    You should avoid using GACUtil to install assemblies to the GAC for the following reasons:
    1. Unless the /r option is used, there is no way to track installation references in the GAC.
    2. GACUtil.exe is part of the .NET Framework SDK and hence is not guaranteed to be on all target machines. Additionally, it is not marked as redistributable and hence you need to check the licensing to make sure you can package it up with your application’s installation image.
    3. Installing using GACUtil.exe does not enable Auto-Repair if the assembly in the GAC is missing (Auto-Repair is possible only with Windows Installer 2.0).

    Sorry to be a bother, but I'm kinda lost. :) I wouldn't complain, as it is at least working, but it's really slow, and the warning from that site about the GAC has me a little concerned that my band-aid solution isn't going to hold up.

     Also, I checked and I did indeed install the toolkit for 2008, not 2005. Thanks.

    Wednesday, January 9, 2008 6:09 PM