BackGroundWorker for .NET 1.1?
- From: Mitchell Vincent <mvincent@xxxxxxxxxxxxxxxx>
- Date: Sat, 18 Feb 2006 13:22:40 -0500
I just read my MSDN magazine from last month and was very pleased to see an article about performance and the small(er) things you can do to improve it.
I have a pretty big database driven winforms application that I've been working on and am very disappointed in the time it takes to show some of these windows. I am doing a lot of data binding and database access in the form's loading event. I do SuspendLayout/ResumeLayout around the code in my _load event but that really only makes it *appear* to "pop" faster.
I read about .NET 2.0's BackgroundWorker support and was intrigued. I can't afford the move to 2.0 yet as virtually no one has it installed, so I'm looking for a solution that will work with .NET 1.1. Is starting a new thread in the load event "proper"? In order to data bind I need to run at least a SELECT query, so is there some harm in binding in a thread other than the main one?
Obviously it does me no good to show a window that the user can't interact with, but even shaving half a second off the load time would be a substantial improvement. Even fractions of a second *appear* to be a long time when just opening a window.
--
- Mitchell Vincent
.
- Follow-Ups:
- Re: BackGroundWorker for .NET 1.1?
- From: Jim Wooley
- Re: BackGroundWorker for .NET 1.1?
- From: Mitchell Vincent
- Re: BackGroundWorker for .NET 1.1?
- From: Carlos J. Quintero [VB MVP]
- Re: BackGroundWorker for .NET 1.1?
- From: Martin
- Re: BackGroundWorker for .NET 1.1?
- From: vbnetdev
- Re: BackGroundWorker for .NET 1.1?
- Prev by Date: WMI Path Problem
- Next by Date: Trying to send mail with an attachment
- Previous by thread: WMI Path Problem
- Next by thread: Re: BackGroundWorker for .NET 1.1?
- Index(es):
Relevant Pages
|