J
Jon Skeet [C# MVP]
Is there anything special about the thread which runs Main in the
Compact Framework?
In my current design, it would be more elegant to create a new thread
and run the UI on that, running the major processing on the entry
thread, than starting a new thread to do the major processing and
running the UI on the entry thread, if you see what I mean. This is
because the UI is basically just reflecting progress - it's not really
"driving" the application.
Does anyone know of any problems with that approach?
Compact Framework?
In my current design, it would be more elegant to create a new thread
and run the UI on that, running the major processing on the entry
thread, than starting a new thread to do the major processing and
running the UI on the entry thread, if you see what I mean. This is
because the UI is basically just reflecting progress - it's not really
"driving" the application.
Does anyone know of any problems with that approach?