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. C#
  4. How to know/identify that installation is done from the application

How to know/identify that installation is done from the application

Scheduled Pinned Locked Moved C#
helptutorial
5 Posts 2 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.
  • S Offline
    S Offline
    Shiby
    wrote on last edited by
    #1

    Hi All, From the application we are waiting, Process.WaitForExit() , for the installation to get over and once over with the installation, does some actions. But in some installations the parent/main process just instantiate the child process and get kill. And child process does the installation and get kill once installation is over. So in my appliation's code. * I start the installation * Store the main process id and wait for exit. * Once parent/main process get kill. * From the task manager list I check all the process whose parent id is equivalent to the one I stored. * If any child process exist then again wait for exit. * Once all the child process get kill then contiune with some actions. But with some installations the child process still remain active even though the installation is over. So in this case I won't be able to continue.. If anyone has solutions to the above problem then please let me know. Thanks & Regards, Shiby Chacko.

    C 1 Reply Last reply
    0
    • S Shiby

      Hi All, From the application we are waiting, Process.WaitForExit() , for the installation to get over and once over with the installation, does some actions. But in some installations the parent/main process just instantiate the child process and get kill. And child process does the installation and get kill once installation is over. So in my appliation's code. * I start the installation * Store the main process id and wait for exit. * Once parent/main process get kill. * From the task manager list I check all the process whose parent id is equivalent to the one I stored. * If any child process exist then again wait for exit. * Once all the child process get kill then contiune with some actions. But with some installations the child process still remain active even though the installation is over. So in this case I won't be able to continue.. If anyone has solutions to the above problem then please let me know. Thanks & Regards, Shiby Chacko.

      C Offline
      C Offline
      Christian Wikander
      wrote on last edited by
      #2

      What kind of installations is this? Installations of other programs that are out of your control? Is it certain installation packages that doesn't work, or is the success depending on something else?

      S 1 Reply Last reply
      0
      • C Christian Wikander

        What kind of installations is this? Installations of other programs that are out of your control? Is it certain installation packages that doesn't work, or is the success depending on something else?

        S Offline
        S Offline
        Shiby
        wrote on last edited by
        #3

        First thanks for your response. From my application, I install some other package that are out of my control. Every installers behaviour is not the same. e.g Case I with editplus installer 1 From my application I start the editplus installation 2 Store the main process id and wait for exit. 3 Once parent/main process get kill. 4 From the task manager list I check all the process whose parent id is equivalent to the one I stored. 5 If any child process exist then again wait for exit. (Now in this case there is no child process created. Goto step 7. ) 6 Once all the child process get kill then contiune with some actions. 7 Continue with rest of the action Case II with Photoshop 1 From my application I start the Photoshop installation 2 Store the main process id and wait for exit. 3 Once parent/main process get kill. 4 From the task manager list I check all the process whose parent id is equivalent to the one I stored. 5 If any child process exist then again wait for exit. (Now in this case there are two child processes get created. Goto step 6. ) 6 Once all the child process get kill then contiune with some actions. 7 Continue with rest of the action Case III with winamp lite 1 From my application I start the winamp lite installation 2 Store the main process id and wait for exit. 3 Once parent/main process get kill. 4 From the task manager list I check all the process whose parent id is equivalent to the one I stored. 5 If any child process exist then again wait for exit. (Now in this case there are two child processes get created. Goto 6.) 6 Once all the child process get kill then contiune with some actions.(but in this case, one process remains active, so could not goto step 7.) 7 Continue with rest of the action In the above case I could not go to step 7 because one installer process remains active. How do I know/get notify that the installation is done/complete. Regards, Shiby

        C 1 Reply Last reply
        0
        • S Shiby

          First thanks for your response. From my application, I install some other package that are out of my control. Every installers behaviour is not the same. e.g Case I with editplus installer 1 From my application I start the editplus installation 2 Store the main process id and wait for exit. 3 Once parent/main process get kill. 4 From the task manager list I check all the process whose parent id is equivalent to the one I stored. 5 If any child process exist then again wait for exit. (Now in this case there is no child process created. Goto step 7. ) 6 Once all the child process get kill then contiune with some actions. 7 Continue with rest of the action Case II with Photoshop 1 From my application I start the Photoshop installation 2 Store the main process id and wait for exit. 3 Once parent/main process get kill. 4 From the task manager list I check all the process whose parent id is equivalent to the one I stored. 5 If any child process exist then again wait for exit. (Now in this case there are two child processes get created. Goto step 6. ) 6 Once all the child process get kill then contiune with some actions. 7 Continue with rest of the action Case III with winamp lite 1 From my application I start the winamp lite installation 2 Store the main process id and wait for exit. 3 Once parent/main process get kill. 4 From the task manager list I check all the process whose parent id is equivalent to the one I stored. 5 If any child process exist then again wait for exit. (Now in this case there are two child processes get created. Goto 6.) 6 Once all the child process get kill then contiune with some actions.(but in this case, one process remains active, so could not goto step 7.) 7 Continue with rest of the action In the above case I could not go to step 7 because one installer process remains active. How do I know/get notify that the installation is done/complete. Regards, Shiby

          C Offline
          C Offline
          Christian Wikander
          wrote on last edited by
          #4

          Is it always the same installation(s) that goes wrong?

          S 1 Reply Last reply
          0
          • C Christian Wikander

            Is it always the same installation(s) that goes wrong?

            S Offline
            S Offline
            Shiby
            wrote on last edited by
            #5

            Yes, it is always the same installation(s) that goes wrong. But there could be some other installation(s) which can behave the same.

            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