ASP.NET custom control with ParseChildren(false) not playing well in the designer or with WAP

I just made a post to the ASP.NET forms for Web Application Projects about this because that’s where it’s affecting me immediately, but honestly I think it’s a bigger problem than that.

Basically I’ve got an ASCX whose code-behind is marked with ParseChildren(false). I then use AddParsedSubObject to handle the adding of controls inside of that with some custom logic. Unfortunately, despite no errors at runtime and no errors in the source view (those little “squiggles”), I end up with this error when I switch to designer view:

Control Designer Error Screenshot

This also seems to prevent WAP from being able to split the file into the new partial classes model. It’s worth noting that I didn’t have this problem with my WAP conversion experiments prior to RC1.

Leave a Reply