What is ASP.NET WebForms equivalent of ASP.NET MVC's ViewData

Question

What are the conventions used in ASP.NET WebForm for passing data to view from code behind? In ASP.NET MVC for example ViewData is a key value collection or a strongly typed class object. So what do people do in case of ASP.NET WebForm.

I know we can create a property or member of a class or add stuff to Page.Items but what else besides that?

Answer 1

I think all the concepts of ASP.NET MVC do not map to ASP.NET Forms since they are two different paradigms of building web app.

In WebForms people mostly deal with controls and set their properties, they don't have to pass data to view as such. However if they do have to do so they use Page.Items or HttpContext.Current.Items or create Page properties that they access in views.

There is no direct equivalent of ViewData or ViewModel in WebForms that is used in practice. Page.Items is the closest thing.

Answer 2

I'm not sure there is a direct equivalent, but the "HttpContext.Current.Items" collection can be accessed from anywhere without having to pass the context (though it does make assemblies dependent on System.Web).