Well the only assembly that I uploaded is my compiled code DLL, I have not uploaded any ASP.NET Ajax DLLs, I thought those would be in the GAC. Do I need to include any DLLs on discountasp.net that I would not need in my local instance? Thanks, Justin
I'm not sure but to keep my Ajax and AjaxControl Toolkit code working I always keep my /bin/ updated here and that does work.
I searched on the forum for this problem but found no matches so excuse me if the problem is addressed somewhere. I am developing locally on VS2008 targeting .NET 3.5 and ASP.NET Ajax, everything works as expected locally. However when I copied my files up to the discountasp.net server I started getting a"Sys is not defined" error in my javascript. All the searching I did in google pointed to a problem with the web.config but mine checks out and it works locally. Is there any option that I need to enable with discountasp.net to get Ajax support? Thanks, Justin
What is the page that produce the error? I'd like to test it on my browser. Bruce DiscountASP.NET www.DiscountASP.NET
it is the default page for the performingat.com domain. I wanted to remove my code as possible cause of the problem so I used an extremely rudimentary sample from the ASP.NET Ajax in Action book and got the same behavior. Thanks for checking this out.
may be these postings will help you http://harishmvp.blogspot.com/2006/11/sys-is-undefined-aspnet-20-ajax.html http://geekswithblogs.net/ranganh/archive/2006/11/24/98276.aspx http://forums.asp.net/p/1040236/1446560.aspx Bruce DiscountASP.NET www.DiscountASP.NET
Thanks for the suggestions but unfortunately none of them worked. I'll keep researching and if I come across a solution I'll post it. If anybody has any other suggestions I would appreciate them. Thanks, Justin
Are you using anything else(Silverlight for example?) on that page ,except AJAX controls?I believe you have already taken that page offline coz I don't see much on the default page? Vikram DiscountASP.NET www.DiscountASP.NET
If you don't find out what's causing the problem PM me. I'll log into your site and see if I can fix it...No charge. Salute, Mark
Turns out it's a timing issue with the js events being wired up too late. Thanks to everybody who offered a suggestion.