A simple include for ASP.NET

re: A simple include for ASP.NET

JesusR — Sun, 11 Oct 2009 23:03:57 GMT

Thx for the info:

In Vb.Net

Public Shared Sub Include(ByRef Pagina As TemplateControl, ByVal Archivo$)

Pagina.LoadControl(Pagina.ResolveUrl(Archivo)).RenderControl(New HtmlTextWriter(Pagina.Page.Response.Output))

End Sub

Usage:

Include(Me, /MiControl.ascx")

re: A simple include for ASP.NET

Jarrett — Sun, 12 Jul 2009 04:54:58 GMT

This is nice. I have a similar widget based include system built into AtomSite (free open-source) and it supports scripts and tail script. Source code is on codeplex.

re: A simple include for ASP.NET

Duncan Smart — Sat, 11 Jul 2009 12:44:06 GMT

The server side  style syntax is actually parsed and processed by ASP.NET so will work anywhere, and would be the simpler solution IMHO.

re: A simple include for ASP.NET

Bertrand Le Roy — Fri, 10 Jul 2009 21:12:29 GMT

@Dave: you win :) I've updated the code to use ResolveUrl and it works fine. I've also changed the type of the first parameter to TemplateControl so that you can now use Include in both pages and user controls.

re: A simple include for ASP.NET

InfinitiesLoop — Fri, 10 Jul 2009 20:48:42 GMT

Oh and this.ResolveUrl will use the current template path as the base, so app relative paths wouldn't be necessary.

re: A simple include for ASP.NET

InfinitiesLoop — Fri, 10 Jul 2009 20:37:18 GMT

ResolveUrl always goes absolute (e.g. /app/foo), ResolveClientUrl goes relative. No?

re: A simple include for ASP.NET

Bertrand Le Roy — Fri, 10 Jul 2009 19:10:37 GMT

@Richard: no. <% %> blocks are executed during render so the include will go in place. Plus, the method is not returning anything so the <%= %> wouldn't do anything.

re: A simple include for ASP.NET

RichardD — Fri, 10 Jul 2009 18:26:12 GMT

Presumable, that should be:

<%= this.Include("Header.ascx"); %>

instead of:

<% this.Include("Header.ascx"); %>

Otherwise, the control output will come before the page output.

re: A simple include for ASP.NET

Bertrand Le Roy — Fri, 10 Jul 2009 18:08:47 GMT

@John: that's absolutely right (see my previous post about master pages).

re: A simple include for ASP.NET

John Bubriski — Fri, 10 Jul 2009 16:25:37 GMT

I just register all of my controls in the web.config, then I never have to worry about registering them on a page-by-page basis. Of course, I still have to do that 1 registration in the web.config, but its easy to copy and paste one, especially if you organize all of your controls into one directory.

Plus, I think you would need the declarative approach to set Properties on the control. In this case, you're including some sort of header, but if its just some sort of "static" header, why not just throw the reference in the master page?