By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,745 Members | 1,897 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,745 IT Pros & Developers. It's quick & easy.

HELP! ASP.NET 2.0 breaks client side javascript! Is WebResource.axd the issue?

P: n/a
Dav
Hi,

I moved over client side javascript code from an asp.net 1.1 project to
an asp.net 2.0 project.
When I view the web page, I get all these "is null or is not object"
javascript errors.

Is there something that I am missing? Is WebResource.axd the issue?

Please post complete solutions and/or links.

I appreciate your help!

Thanks,

David

Jan 12 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Dav said the following on 1/12/2006 1:33 AM in comp.lang.javascript:
Hi,

I moved over client side javascript code from an asp.net 1.1 project to
an asp.net 2.0 project.
When I view the web page, I get all these "is null or is not object"
javascript errors.
Then your JS is flawed.
Is there something that I am missing? Is WebResource.axd the issue?
Most notably you are missing a URL to a sample page.
Please post complete solutions and/or links.


Complete solutions and/or links to what?

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Jan 12 '06 #2

P: n/a
Dav
Then your JS is flawed.
No. It works in VS.NET 2002 and VS.NET 2003 but not in VS.NET 2005! I
know that in VS.NET 2005 WebResource.axd was introduced and I saw that
other people had the same issue (with no real solution).
Most notably you are missing a URL to a sample page.


This is a local project. I am hoping somebody will let me know if there
are any gotchas with VS.NET 2005 and javascript.
Please post complete solutions and/or links.


Complete solutions and/or links to what?


If somebody has a complete solution and/or links to solving this issue
as I know that I am not the only one that has it.

Thank you for your feedback.

If somebody knows why this certain javascript would work in previous
versions of VS.NET but not in VS.2005 that would be appreciated.

David

Jan 12 '06 #3

P: n/a
Dav
Never mind. One of my developers gave me an old version of the
javascript, so it works in VS.NET 2005.

Jan 13 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.