: Monday, January 08, 2007 2:33 PM
> To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
> Subject: Re: [ADVANCED-DOTNET] Threading in ASP.NET
>
> Assuming you're not doing some ajaxy thing, you need to block on the
> main
> thread until all of the other threads complete. Set up some wait
Yep this did the trick; thanks Bob. Thanks for everyone for the replies and
especially thanks for Mike for the link to the article on his blog.
-Pete
On 1/8/07, Bob Provencher <[EMAIL PROTECTED]> wrote:
Assuming you're not doing some ajaxy thing, you need to block on the main
thread until al
> Happy New Year ! I'm having some difficulties with
> threading in ASP.NET.
ASP.NET 1.1 or 2.0?
If you're using 2.0, you should read up on its support for asynchronous
pages. I have a blog entry here[1] that, while focused on one specific
aspect of async page development (timeouts), has so
Some code would probably help, otherwise we're flying blind.
Adam..
-Original Message-
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Peter Vertes
Sent: Monday, January 08, 2007 1:21 PM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: [ADVANCED-DOTNET] Th
Assuming you're not doing some ajaxy thing, you need to block on the main
thread until all of the other threads complete. Set up some wait handles,
kick off the threads, have them signal the handles when completed and have
the main thread wait on them all (or time out).
-Original Message
I would go with AJAX. Then you could have your page
load and still have the
queries you need ran and the controls updated.
-Original Message-
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf
Of Peter Vertes
Sent: Monday, January 08, 2007 2:21 PM
To: ADVANCED
