What would it take to send a page to a browser - and the HTML that comprises
that "page" is 100% generated dynamically?

Specifically, say I have all of the requisite HTML in a string variable. How
do I push that string down to the browser?

My situation is that I have a few .aspx pages containing very little
boilerplate HTML markup and several placeholder controls. At runtime I am
currently injecting the requisite HTML into the placeholder controls. I am
wondering what it would take to eliminate the .aspx file altogether... such
that when the browser requests, for example,
www.DomainName\SomeFolder\File001.aspx I have logic that returns 100% of the
HTML of "File001.aspx" with no such .aspx file having ever existed on disk
on the Web server.



Thanks.

On Oct 9, 7:07 pm, "Frankie" <A...@B.com> wrote:
Do you know about URL Rewriting?
http://www.google.com/search?hl=en&q...+url+rewriting

use an httpmodule instead of a page.

-- bruce (sqlwork.com)

Frankie wrote:

"Alexey Smirnov" <alexey.smirnov (AT) gmail (DOT) com> wrote


Yes - but URL Rewriting has nothing to do with *how* a page is sent to the
browser. It has to do with how pages are *identified.*

On Oct 9, 7:50 pm, "Frankie" <A...@B.com> wrote:
ASP.NET has to do it. Either something like Response.Write() or a
custom HttpModule, as Bruce already suggested

You have to have an Http - addressable endpoint. It could be an ASPX page, or
it could be an ASHX handler, etc. For a page, the only requirement is to have
the
<@Page declaration and specify the codebehind / codefile attribute. What you
do in your code is completely up to you.
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com



"Frankie" wrote: