AJAX Calendar Not Showing on Server


I have a webpage where I have the ajax calendar extender attached to my textbox. When I debug in localhost, the calendar pops up when I click the textbox. After I deploy to my server, it no longer pops up when I click the textbox.

I recently migrated from .NET 2 to .NET 4 (VS 2008 to VS 2010). Before, when I deployed to the server, the calendar extender would work when deploying with .NET 2 as the website asp.net app pool. Now when I deploy with ASP.NET 4.0, it is not working.

Can someone please advise? I will give 500 points.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

is tha ajax calender extender part of the framework or is it an external component?
50fordAuthor Commented:
how can I check? I did not author the original code and the extender was already in place when I took over the process.
are you registering something with the '<%@ Register %>' tag?

for example, for my ajax calendar to work I have to register an external dll like so:
"<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="ajaxToolkit" %>"
Why Diversity in Tech Matters

Kesha Williams, certified professional and software developer, explores the imbalance of diversity in the world of technology -- especially when it comes to hiring women. She showcases ways she's making a difference through the Colors of STEM program.

50fordAuthor Commented:
Yes, we do register it.
Have you checked if there isn't another version out for that same component that targets newer frameworks like 4.0... the old version might not be fully compatible or fully functional
50fordAuthor Commented:
I'm new to AJAX so I apologize if these sound ignorant...

why does it run when I debug on my localhost then?

also, how would I check the version of the current ajax toolkit?

so if I were to download the latest version, do I simply replace the dll file in the bin folder with the newest version that I download? Essentially, how do i upgrade?
there are no stupid or ignorant questions.. I myself am no expert and I learn by asking and sometimes by trial and error, like everyone else. And The problem might not even occour because of this.

from personnal experience the phrase "works on my machine" is something that sooner later a programmer will experience, as it often occurs.
As for checking the version you should try and discover what component you are importing look for their website and look for updates or newer versions. if there is a newer version, backup what you already have, in case anything goes wrong, since we will be deleting some files. Then, after backing up, delete the old dll and any other files related to it, and throught MS VS2010 browse for the reference to the new dll (option: 'Add Reference')

Hi 50ford,
you can check the check under the reference folder from your solution explorer or you can go to the solutions bin folder using windows explorer and looking for the toolkit in the Release/Debug folder.

As apophyspt mentioned, there might be version mismatch. Also, you can check the register directive <@Register...> on top of the page you are trying to access, you might get the version of dll there as well.

Dhawal Seth
50fordAuthor Commented:
thank you everyone for your help. I realized that the web config was the source of error. The handler that calls the ajax dll was still set to 2.0 while everything else had already been updated to 4.0.

below is the handler code that needed to be changed. the v2.0.50727 had to be updated.

<add name="AXD-ISAPI-2.0" path="*.axd" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness32" responseBufferLimit="0"/>

Open in new window


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
50fordAuthor Commented:
thank you to all who offered solutions. I was able to resolve the issue through trial and error as well as research online.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.