Forum Discussion

ryan_perneel's avatar
ryan_perneel
Contributor
6 years ago
Solved

Click Once Application install process

We have a click once application, that I have recently converted to be a TestedApp.  We are hitting issues when we are installing a newer version.

 

I am calling TestedApps.App.Run(), and I can see the application start, but when there is a newer version, we will timeout waiting for the process to start.  We have code to progress through the installation dialogs, but when the exe has not started in the timeout period, we will get an error message stating that the process did not start.

 

Is there anyway to suppress the error message that comes out.

  • You can either make your time out longer or you can make a little loop that looks for the process and if it doesn't find it, waits a bit and goes again, maybe with a message to the log.  That gives you more control over the wait and what's logged, but you still don't want it to wait forever. 

     

    There's also WaitChild or WaitProperty or something similar.  

7 Replies

  • Marsha_R's avatar
    Marsha_R
    Champion Level 3

    You can either make your time out longer or you can make a little loop that looks for the process and if it doesn't find it, waits a bit and goes again, maybe with a message to the log.  That gives you more control over the wait and what's logged, but you still don't want it to wait forever. 

     

    There's also WaitChild or WaitProperty or something similar.  

    • ryan_perneel's avatar
      ryan_perneel
      Contributor

      sorry was away for a bit

       

      The problem with having it in a loop, once the timeout expires, there is an error log message stating cannot find process x.

       

      I am running it like so (process name has been omitted)

       

      TestedApps.APPLICATION.Run()

       

      The timeout is set to 60 seconds.

       

      Once the Run method is invoked, and there is a new version of our software on the server, I am getting the standard "Do you want to install this application" dialog.

       

      We have code to handle that dialog, and it is called directly after the TestedApps.APPLICATION.Run() call, but I do not want to have the "Unable to run "APPLICATION.exe" error message.

      • Marsha_R's avatar
        Marsha_R
        Champion Level 3

        If you don't want to show us details of your code and logs, then I suggest you contact Support directly.  This is the link.

        https://support.smartbear.com/message/?prod=TestComplete

         

        Otherwise, we can only guess at what's really happening from the few details you are providing that makes it difficult.  How you are describing it and what is actually happening may be two different things and we can't help if we can't see.