Comments on: Easy incremental status updates for long requests

By: Brian

Brian — Mon, 16 Jan 2012 01:15:36 +0000

I echo some of the earlier comments – I tried all kinds of ideas from other sites with no luck, and then hit this site, and what a great idea – simple, easy to understand, works like a charm. Great information here.

By: squiel

squiel — Thu, 17 Nov 2011 18:39:13 +0000

Thanks!!!

By: Linh

Linh — Mon, 24 Oct 2011 13:56:02 +0000

When used your code in Chrome browser, when click button, forever spinning appear in tab browser, how to stop it ?

By: corey

corey — Wed, 14 Sep 2011 23:54:00 +0000

this is awesome! thank you so much! cheers from detroit.

By: David T

David T — Tue, 16 Aug 2011 19:43:42 +0000

Merbac – Did you figure out what was going on with your local IIS on Windows 7? BTW, make sure you don’t have Fiddler running while you test as this will cause the symptoms you described.

By: Mercbac

Mercbac — Fri, 17 Jun 2011 17:08:52 +0000

I increased it as high as 600K, but no change. To make it even weirder is that it updates fine if I run it in Visual Studio 2010 development server. And what I set up in IIS is just pure defaults. It shouldn’t have anything to do with my web.config either as it runs fine on my hosting provider’s IIS…
So I built the solution into my site, testing it on VS2010′s server, but I’m still curious to know why my IIS doesn’t want to co-operate.

By: Dave Ward

Dave Ward — Fri, 17 Jun 2011 17:00:11 +0000

You might try increasing the size of the initial 256 byte Response.Write padding. Try increasing it to a huge value like 32,768 to see if that defeats whatever buffering you’re running into, and then lower it from there to determine what the actual value is (I’d be interested in what you find out).

By: Mercbac

Mercbac — Thu, 16 Jun 2011 09:19:59 +0000

This is a great solution, however when I run this on my Win7 SP1 system with IIS, then no updates are displayed from the LongRunningProcess’s Page_Load function until that function ends. Only then are all updates rendered at once.
When I deploy the same thing to my web hosting provider (they also run IIS7) it works just fine. All this regardless of which browser I use, so I do believe there is some IIS setting on my system that’s different from the hosting provider but I just can’t find what that would be.
Any suggestions would be much appreciated.

By: Soren

Soren — Wed, 18 May 2011 14:18:21 +0000

Hep Dave,

Great code – it’s working great – on one of my two loadbalanced servers.

On the first, primary, server the output is first served when the executing method is all done.

On the second if updates fine one line at a time

Have you, or anyone else seen this before ?

By: 缓冲输出 | IT技术问答论坛

缓冲输出 | IT技术问答论坛 — Tue, 18 Jan 2011 17:26:52 +0000

[...] 基本上，我一直在寻找一种方式做一个长期的过程，从不断更新的网页。我还以为是AJAX的路要走，但戴夫一个不错的一篇关于使用Javascript 。本人我的应用程序集成到它的伟大和它的工作对我的客户，但不是我的服务器WebHost4Life。我还有一个服务器@ Brinkster，并决定尝试在那里和它的工作。所有的代码是对我的客户，WebHost4Life和Brinkster相同，因此有明显的东西要和WebHost4Life上。 [...]

By: Dave Ward

Dave Ward — Fri, 14 Jan 2011 04:02:17 +0000

I believe the Response.Flush() calls have the same end result as disabling response buffering on that page. The 256 byte buffering was only happening in IE though, not Firefox or Safari, so I ruled out any server-side fixes.

By: Shiroy

Shiroy — Fri, 14 Jan 2011 03:36:50 +0000

Dave,

Have you thought of using Response.Buffer = false (in ASP.net)

The prevent asp.net from Buffering the page.

However, if it’s IE that’s doing the buffering, then I guess we’re outta luck there!

~Shiroy

By: Jeff

Jeff — Mon, 10 Jan 2011 15:23:04 +0000

As far as I can tell, the Escape key (or stop button) stops the browser postback, but any server-side code executing in your LongRunningProcess.aspx.vb keeps running without any feedback to the user.

My only concern is if a user initiates this long-running process which does a bunch of DB work (clearing out existing records, importing data from another server, etc.) that can take up to 30 minutes to complete, is there a way to “Cancel” the server-side code? If the user starts the 30-minute process and realizes that they made a mistake on one of the input parameters, pressing Esc makes it look like they’ve cancelled it but in reality, records are still being written to the DB. If they then start the process again with different input, the DB will probably end up in an inconsistent state. Any ideas?

By: Usman

Usman — Wed, 29 Sep 2010 01:15:32 +0000

this isnt working for me, if i deployes this on a remote server and try to execute it.

it goes all the way to 100%

By: Paul J. Weighell

Paul J. Weighell — Thu, 06 May 2010 02:51:59 +0000

Great!

Found this after a looooooong search and loads of discarded complex methods.

Works a treat with vb, aspx, web developer 2008 and even master pages.

Remember to set AutoEventWireup=”true” in your LongRunningProcess.aspx

vb example:

Sub Page_Load(ByVal sender As Object, ByVal e As EventArgs)
Response.Write(Space(256))
Response.Flush()
For N = 0 To 10
System.Threading.Thread.Sleep(1000)
UpdateProgress(N, “some message”)
Next
End Sub

Sub UpdateProgress(ByVal PercentComplete As Integer, ByVal Message As String)
Response.Write(“parent.UpdateProgress(” & PercentComplete & “, ‘” & Message & “‘);”)
Response.Flush()
End Sub

Many thanks Mr Ward.