Strange viewstate problem with MCMS

[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

[Alvin Bruney [MVP]]

Do a search at the project level for viewstate being turned off, you have
probably just looked at the page in question. It may be turned disabled in
the custom framework itself.

--
Regards,
Alvin Bruney
------------------------------------------------------
Shameless author plug
Excel Services for .NET is coming...
OWC Black book on Amazon and
www.lulu.com/owc
Professional VSTO 2005 - Wrox/Wiley
"Mark B" <ma*******@yahoo.comwrote in message
news:11*********************@p15g2000hsd.googlegro ups.com...

>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

[Mark B]

I was able to find where viewstate was being turned off that affected
the page. It still doesn't automatically store viewstate but I can add
items to the viewstate so it's a step in the right direction. Please
let me know if you can think of any other ideas.

Thanks,

Mark B
On Mar 18, 4:56 pm, "Alvin Bruney [MVP]" <some guy without an email
addresswrote:

Do a search at the project level forviewstatebeing turned off, you have
probably just looked at the page in question. It may be turned disabled in
the custom framework itself.

--
Regards,
Alvin Bruney
------------------------------------------------------
Shameless author plug
Excel Services for .NET is coming...
OWC Black book on Amazon andwww.lulu.com/owc
Professional VSTO 2005 - Wrox/Wiley

"Mark B" <[e-mail] in message

news:11*********************@p15g2000hsd.googlegro ups.com...

I have anMCMSwebsite 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
viewstatedoes 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

[Alvin Bruney [MVP]]

>It still doesn't automatically store viewstate
There's more digging you need to do, it's probably overridden somewhere
else, I'd go hunt thru the *.config files and in the bowels of the
framework. Do you have current documentation? These *tricks* should be
documented thoroughly because they change the behavior of the framework.

--
Regards,
Alvin Bruney
------------------------------------------------------
Shameless author plug
Excel Services for .NET is coming...
OWC Black book on Amazon and
www.lulu.com/owc
Professional VSTO 2005 - Wrox/Wiley
"Mark B" <ma*******@yahoo.comwrote in message
news:11**********************@d57g2000hsg.googlegr oups.com...

>I was able to find where viewstate was being turned off that affected
the page. It still doesn't automatically store viewstate but I can add
items to the viewstate so it's a step in the right direction. Please
let me know if you can think of any other ideas.

Thanks,

Mark B
On Mar 18, 4:56 pm, "Alvin Bruney [MVP]" <some guy without an email
addresswrote:

>Do a search at the project level forviewstatebeing turned off, you have
probably just looked at the page in question. It may be turned disabled
in
the custom framework itself.

--
Regards,
Alvin Bruney
------------------------------------------------------
Shameless author plug
Excel Services for .NET is coming...
OWC Black book on Amazon andwww.lulu.com/owc
Professional VSTO 2005 - Wrox/Wiley

"Mark B" <[e-mail] in message

news:11*********************@p15g2000hsd.googlegr oups.com...

>I have anMCMSwebsite 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
viewstatedoes 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