Creating a ControlBuilder for the page itself

Dew Drop - November 21, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - November 21, 2008 | Alvin Ashcraft's Morning Dew — Fri, 21 Nov 2008 16:33:16 GMT

PingBack from http://www.alvinashcraft.com/2008/11/21/dew-drop-november-21-2008/

re: Creating a ControlBuilder for the page itself

Nikhil Kothari — Sun, 23 Nov 2008 07:11:27 GMT

I know this is just an example scenario for the file-level control builder, but in fact for this specific scenario, there isn't a need to write a control builder.

Instead one could just remap Label to MyLabel in web.config using the tag mapping feature.

re: Creating a ControlBuilder for the page itself

davidebb — Sun, 23 Nov 2008 19:55:51 GMT

Right, as Nikhil says tag remapping can be used to easily change a control type. This was just some random example to quickly demonstrate that the Page ControlBuilder does in fact get called.

There is no limit to what you can do in your ControlBuilder, especially once you start using ProcessGeneratedCode (see my previous post).

A Little Holiday Love From The ASP.NET MVC Team

you've been HAACKED — Fri, 19 Dec 2008 20:49:10 GMT

A Little Holiday Love From The ASP.NET MVC Team

re: Creating a ControlBuilder for the page itself

Vi — Mon, 22 Dec 2008 21:03:23 GMT

This is not working for me. I've configured my website (not web app) to have my base page:

[FileLevelControlBuilder(typeof(BasePageBuilder))]

public class BasePage : Page

{}

My BasePageBuilder:

public class BasePageBuilder : FileLevelPageControlBuilder

{

public override Type GetChildControlType(string tagName, System.Collections.IDictionary attribs)

{

return base.GetChildControlType(tagName, attribs);

}

And when I put the debug on it, it does not ever hit it.

Anything I'm missing?

re: Creating a ControlBuilder for the page itself

davidebb — Mon, 22 Dec 2008 21:35:35 GMT

Vi, please see the attached sample which is also using a Web Site and not a Web App. If that one works for you, you should be able to identify what is different about your app that causes it not to work.

re: Creating a ControlBuilder for the page itself

Vi — Mon, 22 Dec 2008 22:31:00 GMT

Well it works on the sample. But it still does not hit the debug point on the GetChildControlType override.

When does that get called because it works.

Thanks for the reply.

re: Creating a ControlBuilder for the page itself

davidebb — Mon, 22 Dec 2008 22:36:14 GMT

It only gets called at the time the page gets parsed and compiled, so if it's already compiled you would indeed not hit this. Try just resaving the aspx page and requesting it again, and you'll see that BP getting hit.

re: Creating a ControlBuilder for the page itself

Vi — Mon, 22 Dec 2008 22:51:09 GMT

I figured out the difference. It doesn't appear to work when your page is set to use a seperate code file. (Code-Behind).

That sound right?

re: Creating a ControlBuilder for the page itself

davidebb — Mon, 22 Dec 2008 23:26:15 GMT

You're right! The good news is that it's easy to fix. You just need to add CodeFileBaseClass="MyPage" to the @page directive of the aspx. This is needed because the aspx parser doesn't actually know what base type your code file uses (since it can't parse the code). So it needs that little hint.

re: Creating a ControlBuilder for the page itself

Vi — Tue, 23 Dec 2008 00:16:38 GMT

Yup, that did it!!

Awesome, thanks!

Dynamic Data FAQ

Ricka on Dynamic Data — Wed, 18 Feb 2009 21:52:51 GMT

Please post corrections/new submissions to the Dynamic Data Forum . Put FAQ Submission/Correction in