> I have an oHTML object that I create in my wwServer class. I've added methods to this object that let me evaluate templates and scripts and include them into other pages. It's pretty simple code, actually. In your template or script page the code to include other files would look like:
>
>

>< %= Server.oHTML.GetPage('MyPage.WC') % >
>< some other HTML code >
>< %= Server.oHTML.GetPage('MyPage2.WCS') % >
>
>

>
> I also put all of my generic HTML rendering routines here so that I can use them in any page.

This is exactly what I am trying to avoid.

The problem is that ASP pages have some commands such as INCLUDE. So, assuming a Form.html file has to be included in several pages. So, those ASP pages that need that specific page may have that reference to it. However, from WWC, I may expand a template which may contains that include reference. As this is interpreted by WWC, it won't process the file as ASP so the include won't work. I don't want to be forced to do extra code in WWC just to include other page. Because, if that is the case, whenever I'll expand a template which contains a new include, I'll have to modify my code.