Lost Password? No account yet? Register
Member Area

Software Installation Technologies

May 17th

Home arrow Community arrow External Forums arrow Windows Installer

Windows Installer
Wix - Windows Installer XML Google Group
The Windows Installer XML (WiX) is a toolset that builds Windows installation packages from XML source code. The toolset supports a command line environment that developers may integrate into their build processes to build MSI and MSM setup packages.

  • Re: Files under different directory to be part of one component.
    If you Install the certificate (right click the PFX file, select
    "Install PFX"), complete the dialogs, your "dummy CA" will become a
    trusted CA on the machine. Then, when you open the MSI, you'll get a
    valid Publisher / cert dialog.

  • Re: Files under different directory to be part of one component.
    Thanks very much for the reply. The whole point of doing this, was having something like inhouse certificate. Like, I believe, you can do it on Linux, where you can try to say that you trust that certificate on your machine, and from then on the machine will not complain that it is from unknown publisher. I was wondering when we can do something like that on Linux, why it is not possible on Vista(Windows)?

  • Re: Files under different directory to be part of one component.
    FYI... if you right click the MSI and select Properties, you should
    see the "Digital Signature" tab, in which you'll see the signature
    with your test cert. company name, etc. However, Windows is still
    going to warn you that it's from an Unknown Publisher when you try to
    install it due to CA validation failure.

  • Re: Files under different directory to be part of one component.
    That's because your "test certificate" can't be validated by a CA.
    You'll need to purchase a legitimate Authenticode Cert from Verisign,
    Thawte or some such CA to get a valid Publisher notification.

  • Re: Files under different directory to be part of one component.
    I managed to get this to work.But only thing is, looks like I am missing something here. Even after I do run all the three things. When I try to run my MSI package, it doesnt make any difference. It still says runs from unknown source.

    Please help.

    Thanks

    1) Copy the text below into your favorite editor, save it as a batch

  • Re: Files under different directory to be part of one component.
    Thanks so much for your reply. It seems that I am missing the pvk2pfx.exe from my Bin. I have the other two exe's but this one is missing. I tried looking at the Net, was not too successful in finding this one. I dont know why this pvk2pfx.exe is not part of the SDK itself. Can I download this from somewhere?

  • Re: Files under different directory to be part of one component.
    1) Copy the text below into your favorite editor, save it as a batch
    file under c:\temp (create the dir if it doesn't exist)
    2) Copy your MSI to c:\temp, rename it test.msi (or update the batch
    file below)
    3) Open a Visual Studio command prompt (or, ensure makecert.exe, etc.
    is in your PATH variable)

  • Re: Files under different directory to be part of one component.
    Thanks much. I will try this. Can you please help me with creating a dummy certificate?
    Any suggestions as to how to create these certificates just to see this thing works?

    Thanks much,
    Lizz

    Lizz -
    Sorry... try this (I just tested it, it works... this is the
    command we use in our automated builds)

  • Re: Files under different directory to be part of one component.
    Lizz -

    Sorry... try this (I just tested it, it works... this is the
    command we use in our automated builds)

    signtool.exe sign /f [your cert file name].pfx /p [your cert
    password] /v [your msi].msi

    e.g.

    signtool.exe sign /f mycert.pfx /p mypassword /v myinstaller.msi

  • Re: Files under different directory to be part of one component.
    It gives me an error saying that unable to verify this file using a catalog.
    You can sign MSIs just like you sign an EXE file:
    signtool.exe verify /a /v mypackage.msi
    See: [link]
    For more info. (Of course, you need to purchase a code-signing /
    Authenticode cert)


[ Back ]

DevInstall's Recent

Visitors: 501101

Extended Menu

MSI 4.0: Latest Blogs