Hi Guys,
While going through ASP.NET <http://asp.net/> 4.0 features like ‘ViewStateMode’ – I got a doubt i.e Actually till ASP.NET <http://asp.net/> 3.5 we can’t work by disabling ViewState at Page level and enable it for individual controls – this will not work. To resolve this issue – ASP.NET <http://asp.net/> 4.0 introduced ‘ViewStateMode’ – using which we can able to Disable at Page level and enable it for the individual controls – this is working fine, Even in case of asp.net 3.5, we can enable it for Page and disable it for the individual controls – I have checked it – working fine – what is the problem with this approach? And Even with ‘ViewStateMode’ also we need to make ‘EnableViewState=true’ at Page level – otherwise it won’t work, Other disadvantage of disabling ‘ViewStateMode’ at page level turns-off at server-side also (we can’t use ViewState[“key”]=”Value”; in code behind file). So again we need to enable ‘ViewStateMode’ at Page level and disable for individual controls………the same process as in the ASP.NET <http://asp.net/>3.5 So what Is the main use of ‘ViewStateMode’ ASP.NET <http://asp.net/> 4.0 other than ‘EnableViewState’ ? Can you please clarify me about this. *Thanks & Regards* *P. Bixam* -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
