The Project was originally created as a website, which was recommended early-on by one of the Telerik Support people. Where, they said that it would be easier to deal with than a web app. As, such my Page Directives use CodeFile. Since my last post, I've created a new Solution and moved everything over; it seems to be working fine now, with no runtime errors and no blue squiggly lines.
I do have another RadPersistenceManager issue, as it relates to Page_Load/Unload; but, not sure which forum thread to post. It was recommended to me, on Stack Overflow, to use Page_Load to assign the StorageProviderKey and execute LoadState(), then use Page_Unload to execute SaveState(). I have a RadTabStrip, with (3) tabs, each with a RadGrid. My PersistenceSettings identify each RadGrid. If I simply go into the first tab, make a filter or sort change to the grid, close the page, it saves the filter and sort settings, as it's supposed to. So far, it works great. Where things go bad and where it gets complicated is when I click to another tab, or select another Sort column, or filter on a second column. My Page feels that it needs to Page_Load on each of those; therefore, reloading the saved ViewState. Besides resetting my filter & sort expressions, it's also a performance problem. I shouldn't have to go back to the server and pull data again. It should handle filters & sorts on the client -side...I would think.
So, two questions ...
1) How can I reduce the number of client/server round-trips on a page with multiple tabs & grids?
2) What is Telerik's recommended way of when/where/how to execute LoadState & SaveState?
Thanks in advance.
-john-