Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Ajax and Cassini
cutie
#1 Posted : Thursday, February 8, 2007 5:11:11 PM(UTC)
Groups: Member
Joined: 2/8/2007(UTC)
Posts: 2

Hie,

I am using Ajax.Net Pro by Michael with ASP.Net 2.0. I came across a sample in this website: http://ultidev.com/Forum...t.aspx?g=posts&t=15
The sample is simalar, but different.

I tried the original Ajax.Net pro by using asynchronous function call, but it is not working in Ultidev Cassini. It only works if i use synchronous call. It works fine in IIS.

Does anyone encounter the same problem?
Ultidev Team
#2 Posted : Thursday, February 8, 2007 5:53:34 PM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,253

Thanks: 28 times
Was thanked: 60 time(s) in 59 post(s)
Hi!

We are not familiar with the issue - sorry. Cassini Explorer uses AjaxPro for ASP.NET 1.1 (some pretty old release) and it works alright. This issue may be related to Ajax not finding its scripts. You could easily track failed requests by using Fiddler - simply run it on the same box as your browser and be sure to hit your application using machine name or real IP - not localhost or 127.0.0.1.

Please let us know if you need further help.

Best regard,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
cutie
#3 Posted : Thursday, February 8, 2007 6:39:26 PM(UTC)
Groups: Member
Joined: 2/8/2007(UTC)
Posts: 2

Thanks for the quick reply.

I am using AjaxPro for ASP.Net 2.0. The application was working fine in IIS, but totally not working in apache (both asynchronous, and synchronous), and works in Cassini with synchronous only. I will revert back to the asynchronous application and test it again. If the core js file is not found, how do i determine whether is ajaxpro responsible or cassini responsible?
Ultidev Team
#4 Posted : Saturday, February 10, 2007 12:45:11 PM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,253

Thanks: 28 times
Was thanked: 60 time(s) in 59 post(s)
Hi there.

Sorry for the delay with the response.

If you determined that some requests are failing with Fiddler help you will be able to see what URLs were requested, and based on whether the URL was correct or not you will be able to tell whether it's a web server of an application at fault. Very often IIS developers assume there application will be deployed in a application folder and not in the web server root - that's the single most frequent reason for failed requests.

Best regards,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Rss Feed  Atom Feed
Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You can vote in polls in this forum.