Jump to content
Ketarin forum

lujomu

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by lujomu

  1. As already mentioned, variables of the type 'Textual Content' can be accessed by '$app.Variables.{VariableName}.TextualContent' and variables of type 'Content from URL (Regular Expression)' via '$app.Variables.{VariableName}.CachedContent'.

     

    But I cannot get the value of a 'Content from URL (start/end)' variable. In this case '$app.Variables.{VariableName}.CachedContent' is empty.

  2. Finally got around to test the PowerShell integration a bit. Here are my observations so far.

     

    Working:

    • Common commands (copying, creating directories, etc.) do work.
    • Dot-sourcing of external scripts works, too! (Great for integrating custom functions.)
    • 'Write-Error -ErrorAction Stop' does abort a script with the appropriate status message.
    Issues/suggestions:

    • Having 'Write-Error' anywhere in the script suppresses all output (Write-Warning & Write-Host) to the log file.
    • Warning messages are printed before all the info messages of 'Write-Host', not in order of appearance.


    • Script:
      Write-Host '1. Message 1.'
      Write-Warning '2. Warning 1.'
      Write-Host '3. Message 2.'
      Write-Warning '4. Warning 2.'

      Output:
      > 2. Warning 1.
      > 4. Warning 2.
      > 1. Message 1.
      > 3. Message 2.


    • Could the 'Installing Applications' progress dialog maybe recognize warnings and display a yellow icon and the status 'Installation successful (with warnings)'?
  3. I used exactly that single line as test script. And it does work for the application specific pre-update command, but I am talking about the application specific setup command (http://wiki.ketarin.org/index.php/Setup_instructions).

     

    As this seems to work for some commands but not for others, I checked them each individually (Ketarin v1.7.1.434):

     

    C# test script:



    Abort("Error");


    C# test script results:


    • Default pre-update command in settings: Throws error.
    • Application specific pre-update command: Throws error.
    • Default post-update command in settings: Throws error.
    • Application specific post-update command: Throws error.
    • Command to execute after updating all applications: No error.
    • Application specific setup command: Throws error.


    Batch test script:



    exit 1



    Batch test script results:


    • Default pre-update command in settings: Throws error.
    • Application specific pre-update command: Throws error.
    • Default post-update command in settings: No error.
    • Application specific post-update command: Throws error.
    • Command to execute after updating all applications: No error.
    • Application specific setup command: No error.

     

    As the results differ for both kind of scripts, I doubt this is intentional.

    Can someone else reproduce this? Might this be a bug?

  4. Hi!

     

    I am quite certain this must have come up before, but I can't find any relevant topic.
     
    I am trying to abort a batch setup script. I have tried the following lines:
    exit 1
    exit 2
    exit 3
    exit /B 1
    exit /B 2
    exit /B 3
    But no matter what, Ketarin always prompts "{App}: Installed successfully".
     
    For good meassure I tried the C# equivalent:
    Abort( "Something went wrong!");
    And this yields a nice "{App}: Setup failed (Something went wrong!)" message.
     
    Could someone please enlighten me - what am I missing?
     
    Cheers,
    lujomu
  5. I read in the Wiki (http://wiki.ketarin....update_commands) that exit codes can be used to determine the success/failure of the pre-update commands. So I assumed this would also work on the individual application setup scripts, but no matter what I do, the insallation is always reporterd as successful.

     

    E.g.: I added a new application entry, gave it the name "TEST APP" and created a setup (batch-)script with the single line

    exit 1

    I also tried other exit codes, but the installation is always reported as successful.

     

    Am I missing something?

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.