Setup Deployment: How to prevent a user from unpacking the files to avoid reading the license agreement?

Answered Setup Deployment: How to prevent a user from unpacking the files to avoid reading the license agreement?

  • Thursday, April 05, 2012 10:20 PM
     
     

    I am trying to setup an installer that will unpack files onto the users computer only after they read and agree to a license agreement. (the goal is to release engineering documents without having to use an NDA)

    I am using VS2010 to do this, but the MSI file can be unpacked with a program like 7z zip, and the user can get to the files without ever seeing or agreeing to the license agreement.

    Is this possible to do in VS2010 deployment? Should I try the Installshield LE option in VS?

    Bill

All Replies

  • Friday, April 06, 2012 12:56 AM
     
     

    Select the following option in the Setup Property page ..

    Package files : In cabinet Files(S), Will put the files in a  .Cab file (that i think can we extract thru 7z zip).

    However if you select the option  Package Files : In setup file , file will be pacakged in the .msi file (which cant be extracted thru 7zzip or any other zip)..

    You can also digitally sign your msi with installshield 2011 Premier Edition.

    http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/IWPReleaseSetupExe.htm

    http://helpnet.flexerasoftware.com/installshield18helplib/IWPReleaseSignOptions.htm

    Regards
    Keshav


    • Edited by Keshav Jain Friday, April 06, 2012 12:57 AM edit
    •  
  • Friday, April 06, 2012 6:18 PM
    Moderator
     
     
    In the Add Dialog choices in the setup project's User Interface there's a License Agreement form you can add. In the properties you can browse to an rtf license agreement. The user to chack an Agree radiobutton before they can continue with the install.

    Phil Wilson

  • Thursday, April 12, 2012 6:11 AM
    Moderator
     
     Answered
    Hi Bill,
    As far as I know, setup project don’t have such build- in function. In fact, the customer doesn’t need to use another tool to unpack an msi file. You can unpack it by using msiexec command:
    msiexec /a PathToMSIFile /qb TARGETDIR=DirectoryToExtractTo
    For example, msiexec /a D:\New\Setup1.msi /qb TARGETDIR=D:\New\Test.
    If you want to protect your file, you might can encrypting these files and decrypt them by using a custom action but it might not a good way.
    I’m not familiar with Installshield, you might get the answer in Installshield Forums.
    If you get any other solution, would you mind share it with us?
    Best Regards,

    Bob Wu [MSFT]
    MSDN Community Support | Feedback to us