none
TC2.11.1 InstallShield Custom Action Documentation RRS feed

  • Question

  •  

    Our issue is that the test cases require we document every “CustomAction” found in the installation database (installer msi file). The problem is that from 22 records in our case, there are two only which were created by us. The remaining 20 are from InstallShield so documenting them is problematic.  Any suggestions?  Thanks.

    Wednesday, October 24, 2007 3:24 PM

Answers

  • Venkat, here's the official answer, in hopes other users may get some utility.

     

     

     

    CONFIRMATION OF INSTALLSHIELD 12 CUSTOM ACTION DOC MEETING

    TC2.11.1 REQUIREMENT (PASS)

     

    Lorenzo,

     

    Perfect question, perfectly stated with included information.

     

    Short answer:

    Only your two Custom Actions will need documentation. You are good to go.

     

    Longer answer:

    We are updating our "3rd party" files documentation to exclude binaries the ISV has no control over in their build process.

    As you documented below, please indicate which Custom Actions are part of your Product, and which are from InstallShield.

     

    I will include this Test Case as part of the updated wording regarding "3rd party" files.

     

    Thank you for your question and good luck with Certification.

     

    Here is part of the wording regarding 3rd party files in our almost released Logo FAQ:

     

    Q:

    My application is dependent on 3rd party application and files. Since we don't have any control on those files, we can't put proper icons for those files when we are installing the application. What is the approach for this?

     

    A:

    The ISV should document these 3rd party files when submitting the submission package to the Testing Authority. Otherwise, some test cases may be considered a failure until documentation is received and reviewed, delaying the process of Certification. It is better to document the 3rd party files from the start to avoid this.

     

    A waiver is not required.

     

    Note that this may apply to other test cases as well:

    TC1.4.1: Does the application create files outside the application folder with proper icon, action, and description?

    TC2.8.2: Do the application binaries have valid file version information?

    TC2.11.1 : The intended behavior of each custom action must be documented

    TC3.8.1: Are all executables installed by application signed?

     

     

    Windows Server Logo

    www.InnovateOnWindowsServer.com

     

    Monday, October 29, 2007 5:32 PM

All replies

  •  

    Not sure what you mean by "documenting them is problematic"

    Can you give examples of the CustomActions found in InstallShield that are listed by this test?

     

    Thanks,

    [Venkat] | Windows Server Logo

    www.InnovateOnWindowsServer.com

    Friday, October 26, 2007 2:55 AM
  • Venkat, here's the official answer, in hopes other users may get some utility.

     

     

     

    CONFIRMATION OF INSTALLSHIELD 12 CUSTOM ACTION DOC MEETING

    TC2.11.1 REQUIREMENT (PASS)

     

    Lorenzo,

     

    Perfect question, perfectly stated with included information.

     

    Short answer:

    Only your two Custom Actions will need documentation. You are good to go.

     

    Longer answer:

    We are updating our "3rd party" files documentation to exclude binaries the ISV has no control over in their build process.

    As you documented below, please indicate which Custom Actions are part of your Product, and which are from InstallShield.

     

    I will include this Test Case as part of the updated wording regarding "3rd party" files.

     

    Thank you for your question and good luck with Certification.

     

    Here is part of the wording regarding 3rd party files in our almost released Logo FAQ:

     

    Q:

    My application is dependent on 3rd party application and files. Since we don't have any control on those files, we can't put proper icons for those files when we are installing the application. What is the approach for this?

     

    A:

    The ISV should document these 3rd party files when submitting the submission package to the Testing Authority. Otherwise, some test cases may be considered a failure until documentation is received and reviewed, delaying the process of Certification. It is better to document the 3rd party files from the start to avoid this.

     

    A waiver is not required.

     

    Note that this may apply to other test cases as well:

    TC1.4.1: Does the application create files outside the application folder with proper icon, action, and description?

    TC2.8.2: Do the application binaries have valid file version information?

    TC2.11.1 : The intended behavior of each custom action must be documented

    TC3.8.1: Are all executables installed by application signed?

     

     

    Windows Server Logo

    www.InnovateOnWindowsServer.com

     

    Monday, October 29, 2007 5:32 PM