Asp.net Ajax and jquery used blug together. I don't know who it is?
Currently, all projects are asynchronously requested using Asp.net Ajax, and then the business logic is operated on WebServices, And the return value is
Then, use jquery to process the returned value and the new page.
Yesterday, I made a message and click Submit because it is asynchronous. There are no specific errors, that is, no results.
Why is the insert in my WebServices not executed ..
I remember that I used vs2005 Lite version. Is it a version problem? I just switched to the Professional version,
The problem persists.
After testing for half a day, I finally wrote a method and did not return 8
Print this value after the client asynchronous request is successful. as I do, I always print 1,
I can't figure out how a 1.
I simply deleted prototype, but I didn't reference it (because I recently studied Ajax, so I used a lot of frameworks for comparison ).
There should be no major problems,
For the sake of insurance, after the deletion, print 1
No matter whether it is in IE or FF, I have no discount.
At last, I thought of restarting. It was hard to bear the QQ loose.
Just putProgramTurn off, and then re-open, print 8 ................
Then modifyCode. Welcome to the previous section and find that there is no insert result.
WebServices cannot be debugged.
Printing 2 or 2 always indicates failure
I used my little trick to let WebServices return 1 and judge it on the client.
The result is still printed 2.
So tired ......... It seems that I am looking for a new method.
Prototype advantages, professional, I like professional things, bold use in projects, disadvantages API for JS cainiao, too difficult to understand.
The advantage of jquery is that the API is superb and encapsulates all the Dom. For details about the API, even the value in prototype is also encapsulated with Val.
It is very easy to operate the page by marking the class ID. A newbie can familiarize himself with all the items in the API in one or two days.
ASP. NET Ajax has the advantage that Asp.net is used as the "backend". After Ajax is introduced, the network latency is particularly serious, such as this. textbox1 point.
If it is not displayed, all the labels on the page are gray, and the color will change after a while.
Then ASP. Net Ajax is built on ASP.net Ajax-eanble web sit, not like prototype or jquery.
Reference. If you want to configure it, It is very troublesome.
Another point is prototype, jquery.Source codeCan be parsed, ASP. NET Ajax source code does not want to read.
When starting URL rewriting, get the requested address in global and then convert it. ASP. NET Ajax is better than what we should first change the address to, such as XSD.
Finally helpless or use MS urlriwrter set up.