You can also set Response.Buffer = False at the top of your page and you
won't have to do all the Response.Flush() commands. Essentially you're
turning off bufferring so all responses are immediately sent to the browser.

tip: This also helps when a part of the page is taking a long time to load
while the rest of the page is fast. Instead of holding everybody hostage
you'd turn off the buffer and the slow image etc would load on its own sweet
time.

That's a good question--I've never had a great deal of luck styling ListBox
controls.  If I need really heavy duty theming, I tend to create composite
controls of my own.

If you wanted the box to expand dynamically (rather than scroll), that's
possible too..  You could refactoring out the .Insert command and do something
like:

       protected void Page_Load(object sender, EventArgs e)
       {
           // Put an "item" for each line in the "console" output.
           ConsoleWriter(ConsoleOutput, "Collecting user input ...");
           ConsoleWriter(ConsoleOutput, "Saving user profile ...");
           ConsoleWriter(ConsoleOutput, "Generating report in PDF ...");
           ConsoleWriter(ConsoleOutput, "Dispatching report to user email
...");

           ConsoleWriter(ConsoleOutput, "Collecting user input again... ");
           ConsoleWriter(ConsoleOutput, "Saving another user profile ...");
           ConsoleWriter(ConsoleOutput, "Generating another report in PDF
...");
           ConsoleWriter(ConsoleOutput, "Dispatching the final report to
user email ...");
       }

       protected void ConsoleWriter(ListBox listBox, string textToWrite)
       {
           listBox.Items.Insert(0, textToWrite);
           listBox.Rows = listBox.Items.Count + 1;

       }

That'll keep the ListBox 1 line "bigger" (that may not even be necessary,
can try with and without the +1) than the data it's holding.  I'm sure others
on here have some creative ideas as well--I've just never sat down and hacked
out the actual ListBox control.  :)

Good luck!

-dl

--
David R. Longnecker
http://blog.tiredstudent.com

On Dec 21, 12:03 pm, bruce barker
<brucebar...@discussions.microsoft.com> wrote:

I just tried your approach, like what you've said, it will not appear
until all processing is done.  In other words, you don't see those
output one after another with some pause in between them, even if you
use Thread.Sleep(5000) after each output. It does not work.  You see
them all at once when the page renders.

Not sure how DotNetNuke does it for their installation process.