In my inaugural post, I described a problem I had with a WebMethod erroring out instantly on the client, accompanied by a puzzling message in the Event Log, regarding viewstate.
On a whim, on that site, I decided to “publish” the website from within VS 2005 to a separate directory. I set up another virtual directory within IIS to point to that directory, loaded up the site and IE, and all my WebMethod calls were working!
From IE6, that is.
From FireFox, none of the calls work on the published website....
...the first time. If I click on the link that calls the WebMethod again (after getting the instant error), it works fine. Very weird.
In this post, I mentioned tearing my hear out because I couldn't get a gridview to work right with the update panel. Today I decided to just start on a fresh web form and everything seems to be working fine.
I did learn that an updatepanel without any triggers will consume any server-side event that fires inside of it (ie, to get paging and sorting working you don't need to explicitly specify triggers to handle those events). I also learned that (and this isn't related to Atlas) a gridview's page and sort events also fire off RowCommand events...which I guess make sense since the header is a “row” and the pager thing is also a “row”.
Still trying to figure out the updatePanel inside of a userControl thing figured out, I'll keep you posted.