Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. Process::HasExited always true

Process::HasExited always true

Scheduled Pinned Locked Moved .NET (Core and Framework)
csharpcomquestion
6 Posts 5 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    piul
    wrote on last edited by
    #1

    Am I the only fool using .NET in here?... haha In the process I´ve explained here the property Process::HasExited is true from the moment the process starts. The same occurs with the method void extProcessWorkCompleted (System::Object^ /*sender*/, System::ComponentModel::RunWorkerCompletedEventArgs^ e) which is called when the process starts, and not when it actually finishes. Has this something to do with the process´s code or am I doing something wrong?

    L R L 3 Replies Last reply
    0
    • P piul

      Am I the only fool using .NET in here?... haha In the process I´ve explained here the property Process::HasExited is true from the moment the process starts. The same occurs with the method void extProcessWorkCompleted (System::Object^ /*sender*/, System::ComponentModel::RunWorkerCompletedEventArgs^ e) which is called when the process starts, and not when it actually finishes. Has this something to do with the process´s code or am I doing something wrong?

      L Offline
      L Offline
      Luc Pattyn
      wrote on last edited by
      #2

      piul wrote:

      Am I the only fool using .NET in here?

      I don't know.

      piul wrote:

      am I doing something wrong?

      Most probably. :|

      Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum

      Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.

      P 1 Reply Last reply
      0
      • L Luc Pattyn

        piul wrote:

        Am I the only fool using .NET in here?

        I don't know.

        piul wrote:

        am I doing something wrong?

        Most probably. :|

        Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum

        Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.

        P Offline
        P Offline
        piul
        wrote on last edited by
        #3

        Well... I was trying to make a joke, nothing else. I´m sorry if that dissapointed someone.

        R 1 Reply Last reply
        0
        • P piul

          Well... I was trying to make a joke, nothing else. I´m sorry if that dissapointed someone.

          R Offline
          R Offline
          Ravi Sant
          wrote on last edited by
          #4

          No one is disappointed. It is NOT sensible to rewrite about same question. And we have Message Type, which has Joke in it. If you want to Joke, come and have a good joke at Lounge.

          1 Reply Last reply
          0
          • P piul

            Am I the only fool using .NET in here?... haha In the process I´ve explained here the property Process::HasExited is true from the moment the process starts. The same occurs with the method void extProcessWorkCompleted (System::Object^ /*sender*/, System::ComponentModel::RunWorkerCompletedEventArgs^ e) which is called when the process starts, and not when it actually finishes. Has this something to do with the process´s code or am I doing something wrong?

            R Offline
            R Offline
            RobCroll
            wrote on last edited by
            #5

            Foolish, The extProcessWorkCompleted event is raised when the process starts? Definitely someone has got it wrong. Couldn't see any MSDN documentation on extProcessWorkCompleted so I'm guessing it's you.

            "You get that on the big jobs."

            1 Reply Last reply
            0
            • P piul

              Am I the only fool using .NET in here?... haha In the process I´ve explained here the property Process::HasExited is true from the moment the process starts. The same occurs with the method void extProcessWorkCompleted (System::Object^ /*sender*/, System::ComponentModel::RunWorkerCompletedEventArgs^ e) which is called when the process starts, and not when it actually finishes. Has this something to do with the process´s code or am I doing something wrong?

              L Offline
              L Offline
              Lost User
              wrote on last edited by
              #6

              piul wrote:

              The same occurs with the method void extProcessWorkCompleted (System::Object^ /*sender*/, System::ComponentModel::RunWorkerCompletedEventArgs^ e) which is called when the process starts, and not when it actually finishes.

              Some executables finish immediately after spawning a child-proces. Can you compare the Process-ID of the executable that you started to the one that seems to be running?

              I are Troll :suss:

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups