Forum Discussion

ryan_perneel's avatar
ryan_perneel
Contributor
6 years ago

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 s...
  • Marsha_R's avatar
    Marsha_R
    6 years ago

    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.  

Marsha_R's avatar
Marsha_R
Moderator

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
6 years ago

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
    Moderator
    6 years ago

    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.

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      6 years ago

      TestedApps.Run has built into it that timeout to wait for the process.

       

      Instead of using TestedApps.Run to run the application, you could use the Exec or Run method of WShell to execute the command line to launch the application and tell it to not wait for the command line to return.  That way you could launch the application, put your own code in to check for the popup and process from there.

      • ryan_perneel's avatar
        ryan_perneel
        Contributor
        6 years ago

        That is what we were doing, but recently we added CEF components to the WPF application, and from what support is telling/told me, i need to launch the application as a TestedApp to beable to view CEF components (and there is another bug where Click Once applications launched via TestedApps is still not able to see CEF, i have been told that is being fixed soon)

         

        so it seems that I am in an interesting situation, where I need to launch the app via testedapps, but on the initial install of a new version, i will have to deal with an error message?

         

        Thanks!