This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Packaging with Mobile2Market Certificate
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 01, 2008
04:40 PM
Packaging with Mobile2Market Certificate
I'm working on packaging an application for Windows Mobile for one of our customers and they are considering using Verisign for their Mobile2Market certificate provider and I'm working on figuring out how to get the CAB files signed with the Verisign Mobile2Market certificate and get those signed CAB files incorporated in the MSI.
So far, the only solution I've found is to build the installation goes something like this and is completely manual:
1. Extract the CAB files that need to be signed from the MSI (or use the CAB files from the CEApps directory beneath the configuration being built),
2. Sign them with the initial code-signing cert provided to me from Verisign,
3. Post those to the Verisign site,
4. Download them after they've been signed with the cert chained to the Microsoft Mobile2Market root cert, and then
5. Insert those signed files back into the MSI. (Using Orca or InstallShield as the MSI editor.)
Any different ideas for solving this problem? Has anyone found an automated solution using InstallShield as the setup packaging IDE?
So far, the only solution I've found is to build the installation goes something like this and is completely manual:
1. Extract the CAB files that need to be signed from the MSI (or use the CAB files from the CEApps directory beneath the configuration being built),
2. Sign them with the initial code-signing cert provided to me from Verisign,
3. Post those to the Verisign site,
4. Download them after they've been signed with the cert chained to the Microsoft Mobile2Market root cert, and then
5. Insert those signed files back into the MSI. (Using Orca or InstallShield as the MSI editor.)
Any different ideas for solving this problem? Has anyone found an automated solution using InstallShield as the setup packaging IDE?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 07, 2009
08:01 AM
Does anyone have a better solution for this yet?
I'm now using IS 2010, and have bumped into the same problem.
Is there a setting to keep the .cab-files separate (i.e. not include them into the msi)?
I'm now using IS 2010, and have bumped into the same problem.
Is there a setting to keep the .cab-files separate (i.e. not include them into the msi)?