M
Mark B
I have an MCMS website that I inherited. It was originally built
in .NET 1.1 and then ported to .NET 2.0. They built it with inherited
base classes to mimic what is now done with master pages.
So much for the background. I'm building a new page that's pulling
information from a database. The initial input has a dropdown list
that populates dynamically and a couple labels that I'm using for
housekeeping duties. The problem is that neither the dropdown or the
labels maintain state on postback.
To verify that it's not the form itself, I created a new template page
that does not use the original format. It just has my new form. This
works fine. When I insert it into the existing page framework, the
viewstate does not work.
I checked to see that there are no page directives that disable
viewstate. Other than that, I'm really kind of stumped on where to
look next.
Any ideas are most appreciated.
Thanks,
Mark B
in .NET 1.1 and then ported to .NET 2.0. They built it with inherited
base classes to mimic what is now done with master pages.
So much for the background. I'm building a new page that's pulling
information from a database. The initial input has a dropdown list
that populates dynamically and a couple labels that I'm using for
housekeeping duties. The problem is that neither the dropdown or the
labels maintain state on postback.
To verify that it's not the form itself, I created a new template page
that does not use the original format. It just has my new form. This
works fine. When I insert it into the existing page framework, the
viewstate does not work.
I checked to see that there are no page directives that disable
viewstate. Other than that, I'm really kind of stumped on where to
look next.
Any ideas are most appreciated.
Thanks,
Mark B