Your patch which I applied on the 13th caused this bug

Moving the call to LoadPage() out of Page_Load and into On_Init in Default.aspx.cs was the change that broke it.

I moved it back to Page_Load and it works again.

Joe

I have no problem using viewstate from inside modules I would rather see the code where you are having this problem and see if I can figure out why you are having this issue.

I believe the correct place to load controls is in Page_Load

Joe

I use it in FileManager.ascx

I think the issue you are having is that ViewState is disabled by default in Default.aspx.cs according to the Web.config setting DisablePageViewStateByDefault

This is for performance, if a module in the page needs viewstate it is up to the module to call
Page.EnableViewState = true;

in page load of the module

Or if you don't like this behaviour you can set DisablePageViewStateByDefault = false in Web.config

Joe

1. ok

2. As above, if I agree with your patch and see no problems I'll go along with that change.

3. I found measurable performance improvement by disabling ViewState at the page level in my load tests. Since I generally try to avoid using viewstate even in my modules (I mean I use it but I try to keep it to a minimum) it seems a reasonable setting to me.

In general I try to avoid using postback in the module control but instead try to link to a separate edit page. In some cases use of postback can't be avoided in the module but if it can be avoided I try to avoid it. Modules that use postback have difficulty being cached and may cause strange behavior in other modules that happen to be on the same page during postback. i.e if there is another module on the page using code like if(!Page.IsPostBack)

Joe

Sorry for the delay in replying.

Thanks for the updated patch!

I think I did misunderstand, anyway I think viewstate is enabled at the Page level by default so I thought you might mean it was odd to disable it.

Cheers,

Joe