Re: Windows Forms advice
- From: "Kevin Spencer" <unclechutney@xxxxxxxxxxxx>
- Date: Fri, 16 Feb 2007 14:14:33 -0500
A Windows Forms application runs in a Single-Threaded Apartment model, with
a single thread handling the execution of the UI. Any threading you do will
have to be done by non-UI classes. Putting various forms into different
assemblies has no effect on the application, though.
--
HTH,
Kevin Spencer
Microsoft MVP
Software Composer
http://unclechutney.blogspot.com
I had the same problem once. Fixed it using the same solution.
"abhiM" <abhi.menon@xxxxxxxxx> wrote in message
news:1171644320.145803.248930@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
This is a very general question. I am about to embark on
developing a new application (Windows Forms based). All the business
logic, external interfaces etc have already been developed and are
available as ready to use libraries.
This application is going to be multi-threaded. Is it recommended
to have each of the different forms or at least a couple of related
forms packaged into separate libraries. Is such a packaging going to
have any effect on the multi-threaded nature of the application. This
is the first time I am using threading and I need to use threads to
display the status of some of the devices in the system in real time.
Any recommendations and any advice is greatly appreciated.
Thanks,
AM
.
- References:
- Windows Forms advice
- From: abhiM
- Windows Forms advice
- Prev by Date: Re: Next File (System.IO)
- Next by Date: Re: The record cannot be deleted or changed because table
- Previous by thread: Windows Forms advice
- Next by thread: Maximized MDI Child form with no titlebar shifts form
- Index(es):
Relevant Pages
|