AJAX Calendar Not Showing on Server
Hi,
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.
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.
APoPhySpt
is tha ajax calender extender part of the framework or is it an external component?
ASKER
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="AjaxControlToolk
for example, for my ajax calendar to work I have to register an external dll like so:
"<%@ Register Assembly="AjaxControlToolk
ASKER
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
ASKER
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?
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')
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.
Regards,
Dhawal Seth
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.
Regards,
Dhawal Seth
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thank you to all who offered solutions. I was able to resolve the issue through trial and error as well as research online.