i installed the new ctp(beta 1) and removed it and go buck to july ctp atlas
big problems that my projects fails:
1. page.clientscript.registerstartupscript - not working
insted i found some bizar fix like Microsoft.Web.Ui.Scriptmanager.RegisterStartupScript(....)
the problem with it that (allserver controls and some client click events that use 'page.clientscript.registerstartupscript' need to be updated somehow - and who has alot of server controls and alot of code it's alot of fixing and debbuging)
2. pageMethods - not working
and even the fix is no good for a system that uses pageMethods that reads data from aspx file
because the method(function) must bestatic c# /shared on vb
and becasue the need to be static
viewstate -can't exist in static function,this/Me (this.someControlName) can't exist in static function
so my suggest is (make some compatibility) to july ctp of atlas
any why i am done with this beta realese
p.s.
great job atlas team
hello.
let me add my comments:
1. it's not a bizarre fix...it's a way to ensure that everything works. it's funny that you mention that since i was under the impression that many controlos broke because the clientscriptmanager methods were used...
2. don't tell me that you were using page methods for anything...could you give me an example where you need a page method? i mean, passing everything to the server just to get a response back is not really a performant behavior...
example u ask:
there are many ways of transfering data between pages
and yes PageMethods are one of them
i transfer from child window data to parent window with pagemethods, in parent window some function
commited and creats file with all inputs from child and parent
i got pages that use this method, that's why i need pagemethod like july ctp
----------------------------------
before atlas i used the dll below
and the way i use pageMethod i used this ajaxpro dll
so -compatibility - if no the have torebuild with every new ctp or beta
http://ajaxpro.schwarz-interactive.de/
did u ever used this ajax ? (link above)
before the big "atlas" of microsoft
there was some great dll called "ajax pro" byschwarz
and i build my system ajax on is dll.
hello again.
well, if you such ajax believer (which i'm not), then you surelly know that true ajax programming is on the client. this means you use javascript and xml and perform remote web method calls to get the data. pagemethod as it was presented in previous release was nonsense: you send everything back to the server just to get a result back on the server and in all cases, you really didn't need all that info that was sent back to the server. using it means wasting network bandwith. so i'm really glad they've removed it from the bits.
regarding ajax pro, nothing prevents you from still using it...
No comments:
Post a Comment