why should i not use magic ajax?

can any tell me , what are the disadvantages of magic ajax?

or any bottle neck? its very easy to use, and its working, but i have to take desccion either to use it or not? please share your experience with magi?

Magic AJAX might not integrate with ASP.Net as seamlessly as ASP.Net AJAX. Remember ASP.Net AJAX and ASP.net both are build by the same company Microsoft. They know better how both work so they can make integration very tight. Furthermore, ASP.Net AJAX is free why would anyone go for Magic AJAX?

It doesn't look very mature, compared to ASP.NET AJAX, and you'd be drastically limiting your support options by going with an obscure framework.

Why avoid ASP.NET AJAX?

hmm, ok thanks for both of you, i dont know i install ajax tookit but its not working, :(

and i found magic ajax very easy,,, any way, i ll try my best to use asp.net ajax rather magic,

Thanks Alot

hai magic ajax for asp.net 2.0 is not supporting page store mode session..we used magic ajax for our application asp.net 1.1 .after porting it to asp.net 2.0 ..problem comes ,in asp.net 2.0 magic ajax only support nostore mode.our code is based on session mode...thanks
hai magic ajax for asp.net 2.0 is not supporting page store mode session.. we used magic ajax for our application asp.net 1.1 . after porting it to asp.net 2.0 ..problem comes ,in asp.net 2.0 magic ajax only support nostore mode. our code is based on session mode... thanks

I started using Magic Ajax over a year a go just before "Atlas" (now called MS Ajax) came out. I have to say it was easy to get it to work but I started to problems with getting things like paging on gridviews to work. The problem with this was that I just couldn't get any help or support on the issue, so I switched to Atlas\MS Ajax and never looked back.

Go with MS Ajax, at least you are guaranteed upgrades and updates to it and fairly good support from the community and MS. And also loads of documentaion and examples on the web. Magic Ajax just cant compete with that and will eventually die out. You need to work with things that have a future and will be supported and upgraded. If you are building asp.net apps and want to use Ajax then you should use MS Ajax, there is no reason not to.

what about session mode in magic ajax in asp.net 2.0