I am getting a strange Error with the CalendarExtender,
The Error is in the ScriptResource.axd File On Line 1162 the Error with
value = Date.parseLocale(text, this.get_format());
It occurs in FF and IE , I looked at it in firebug and it the error it shows says Date.parseLocale is not a function.
The strange thing is that this error shows up on my test server but not on my local system and the CalendarExtender is inside the new tabcontainer which shows the tabs just fine.
bump - any updates on this? I have the exact same problem. Date.parseLocale is not defined in ScriptResource.axd when I use a CalendarExtender, and it works fine locally.
As far as I can tell, this doesn't "break" the control -- but the user has look at the error indicator at the bottom of the screen.
I too am having this problem but not on 2 different machines. I'm having it between projects on the same machine and have done the following:
To start off, this project has evolved from Atlas, to AJAX beta through RC1 and RC2 to the full release version. The problem only happens when I click on the text box associated with the calendar and there is already a date in the textbox. When it does this
it tries to parse the date but the Date class object in the JS code from the axd file doesn't have a parseLocale method, instead it is named localeParse.
So far, I have tested the AjaxControlToolkit project which works just fine. I created my own web project and mirrored the references and includes from my broken project even using the current web config from my other project and the test page works just
fine in the new project. If I put a breakpoint on the line of code that breaks:
value = Date.parseLocale(text, this.get_format());
I can see the Date object is different in the 2 projects. The line of code above is from the _parseTextValue : function(text) function in the Calendar control axd Script Resource. When I look at the axd include in the script explorer that has the 2 different
Date parseLocale/localeParse methods, the files are obviously different. The thing I don't get is where the old version is coming from. I have removed all of the old AJAX/Atlas code from my machine. The only version of the AJAX code in the C:\Windows\assembly
folder are the 1.0.61025.0 versions.
The one difference I had a coworker point out to me was the fact my test project and the AjaxControlToolkit project were both running from the ASP NET Development server. I'm guessing my local IIS instance may be caching the old AJAX code somewhere but
that's just a guess. Any input on this would be greatly appreciated.
UNLESS someone like you cares a whole awful lot, nothing is going to get better. It's not!
Wow, I can't believe I wasted so much time on such a simple problem... After installing the new AJAX, I never did an aspnet_regiis -i to reinstall asp.net 2.0 for IIS on my machine. After thinking about how it was only happening with the app I'm running
out of my local IIS install, I figured I'd try to re-register in the hopes it would fix the problem and voila! problem solved. It works like a charm now.
Just in case someone reads this and is unfamiliar with aspnet_regiis it is the app you use to register the aspnet codebase in IIS. It can be found in your windows folder in the following heirarchy:
(Windows)\Microsoft.NET\Framework\(version you want to use)\aspnet_regiis.exe
so for me, it was C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe and you need to run it with the -i flag to reinstall.
I hope this helps someone :)
UNLESS someone like you cares a whole awful lot, nothing is going to get better. It's not!
Thanks! :) Yeah, I didn't expect I would have to reregister in IIS. I figured if that was necessary, the AJAX installer would have done so. (hint hint) Either that or they would have mentioned it somewhere in the release notes. I'm just glad I figured it
out before it drove me comletely insane. Being able to help others is an added bonus.
UNLESS someone like you cares a whole awful lot, nothing is going to get better. It's not!
tennisDave
0 Points
3 Posts
New CalendarExtender Error in ScriptResource.axd
Jan 26, 2007 11:49 PM|LINK
I am getting a strange Error with the CalendarExtender,
The Error is in the ScriptResource.axd File On Line 1162 the Error with value = Date.parseLocale(text, this.get_format());
It occurs in FF and IE , I looked at it in firebug and it the error it shows says Date.parseLocale is not a function.
The strange thing is that this error shows up on my test server but not on my local system and the CalendarExtender is inside the new tabcontainer which shows the tabs just fine.
Any help would be appreciated.
Thanks
</div>
ajax CalendarExtender Error
CaptainGs
Member
10 Points
5 Posts
Re: New CalendarExtender Error in ScriptResource.axd
Jan 29, 2007 11:41 AM|LINK
bump - any updates on this? I have the exact same problem. Date.parseLocale is not defined in ScriptResource.axd when I use a CalendarExtender, and it works fine locally.
As far as I can tell, this doesn't "break" the control -- but the user has look at the error indicator at the bottom of the screen.
CaptainGs
Member
10 Points
5 Posts
Re: New CalendarExtender Error in ScriptResource.axd
Jan 29, 2007 11:59 AM|LINK
btw - this appears to only happen if you use server side code to set the control that the CalendarExtender is attached to.
the_lorax
Member
293 Points
65 Posts
Re: New CalendarExtender Error in ScriptResource.axd
Jan 29, 2007 05:32 PM|LINK
I too am having this problem but not on 2 different machines. I'm having it between projects on the same machine and have done the following:
To start off, this project has evolved from Atlas, to AJAX beta through RC1 and RC2 to the full release version. The problem only happens when I click on the text box associated with the calendar and there is already a date in the textbox. When it does this it tries to parse the date but the Date class object in the JS code from the axd file doesn't have a parseLocale method, instead it is named localeParse.
So far, I have tested the AjaxControlToolkit project which works just fine. I created my own web project and mirrored the references and includes from my broken project even using the current web config from my other project and the test page works just fine in the new project. If I put a breakpoint on the line of code that breaks:
value = Date.parseLocale(text, this.get_format());
I can see the Date object is different in the 2 projects. The line of code above is from the _parseTextValue : function(text) function in the Calendar control axd Script Resource. When I look at the axd include in the script explorer that has the 2 different Date parseLocale/localeParse methods, the files are obviously different. The thing I don't get is where the old version is coming from. I have removed all of the old AJAX/Atlas code from my machine. The only version of the AJAX code in the C:\Windows\assembly folder are the 1.0.61025.0 versions.
The one difference I had a coworker point out to me was the fact my test project and the AjaxControlToolkit project were both running from the ASP NET Development server. I'm guessing my local IIS instance may be caching the old AJAX code somewhere but that's just a guess. Any input on this would be greatly appreciated.
the_lorax
Member
293 Points
65 Posts
Re: New CalendarExtender Error in ScriptResource.axd
Jan 29, 2007 07:37 PM|LINK
Wow, I can't believe I wasted so much time on such a simple problem... After installing the new AJAX, I never did an aspnet_regiis -i to reinstall asp.net 2.0 for IIS on my machine. After thinking about how it was only happening with the app I'm running out of my local IIS install, I figured I'd try to re-register in the hopes it would fix the problem and voila! problem solved. It works like a charm now.
Just in case someone reads this and is unfamiliar with aspnet_regiis it is the app you use to register the aspnet codebase in IIS. It can be found in your windows folder in the following heirarchy:
(Windows)\Microsoft.NET\Framework\(version you want to use)\aspnet_regiis.exe
so for me, it was C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe and you need to run it with the -i flag to reinstall.
I hope this helps someone :)
CaptainGs
Member
10 Points
5 Posts
Re: New CalendarExtender Error in ScriptResource.axd
Jan 29, 2007 08:20 PM|LINK
bless you sir -- that was a nice catch [:)]
I didn't even think to do that when I installed the release Ajax -- all I did was flush the IntelliSense cache (another headache from another day).
the_lorax
Member
293 Points
65 Posts
Re: New CalendarExtender Error in ScriptResource.axd
Jan 29, 2007 08:52 PM|LINK
Thanks! :) Yeah, I didn't expect I would have to reregister in IIS. I figured if that was necessary, the AJAX installer would have done so. (hint hint) Either that or they would have mentioned it somewhere in the release notes. I'm just glad I figured it out before it drove me comletely insane. Being able to help others is an added bonus.
David Anson
Star
8728 Points
1847 Posts
AspNetTeam
Re: New CalendarExtender Error in ScriptResource.axd
Jan 30, 2007 12:15 AM|LINK
http://dlaa.me/
http://blogs.msdn.com/b/delay/
This posting is provided "AS IS" with no warranties, and confers no rights.
indiguy
Member
123 Points
46 Posts
Re: New CalendarExtender Error in ScriptResource.axd
Feb 02, 2007 08:04 PM|LINK
sburke_msft
Contributor
4396 Points
770 Posts
AspNetTeam
Re: New CalendarExtender Error in ScriptResource.axd
Feb 02, 2007 09:07 PM|LINK