Results 1 to 8 of 8

Thread: Need to use a thread instead of a process? [C# 2002]

Hybrid View

  1. #1

    Thread Starter
    Hyperactive Member
    Join Date
    Apr 2003
    Posts
    308

    Re: Need to use a thread instead of a process? [C# 2002]

    Isn't that only for .NET 2.0? Or is it also available in .Net 1.1 (C# 2002)?
    Can you possibly provide more details - never worked with "backgroundworker"'s before...

    Thanks,

  2. #2
    Registered User nmadd's Avatar
    Join Date
    Jun 2007
    Location
    U.S.A.
    Posts
    1,676

    Re: Need to use a thread instead of a process? [C# 2002]

    Quote Originally Posted by Shaitan00
    Isn't that only for .NET 2.0? Or is it also available in .Net 1.1 (C# 2002)?
    Can you possibly provide more details - never worked with "backgroundworker"'s before...

    Thanks,
    Sorry, but the BackGroundWorker only became available in 2.0.

  3. #3

    Thread Starter
    Hyperactive Member
    Join Date
    Apr 2003
    Posts
    308

    Re: Need to use a thread instead of a process? [C# 2002]

    Is a thread therefore the only way to go?
    Process was great because I could wait for it to exit, get the return code, etc... and the process simply launches an executable file (run.exe) so I didn't think threading was absolutly necessary for this requirement...

  4. #4
    Arabic Poster ComputerJy's Avatar
    Join Date
    Nov 2005
    Location
    Happily misplaced
    Posts
    2,513

    Re: Need to use a thread instead of a process? [C# 2002]

    You'll need another thread(s) to start and control your process, i.e. you'll use both concepts (threads & processes).
    Using multi-threading might cause you some UI problems, so make sure you do a research before you dig into coding
    "I'm not normally a praying man, but if you're up there, save me... Superman!" - Homer Simpson
    My Blog

  5. #5

    Thread Starter
    Hyperactive Member
    Join Date
    Apr 2003
    Posts
    308

    Re: Need to use a thread instead of a process? [C# 2002]

    See - I get the fact of using a thread if I am to be making changes on the form (frmMain) while the process is running - but in this case I am only doing one thing at a time (which is why I thought using a process would be fine) - the UI is just there displaying to the user but no changes are happening on it...

    So it is normal that when I .Start() my process the form starting it gets automatically hidden?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width