Software Deployment

creating a transform is easy too just use tuner.Please remember that not everyone uses the same packaging tool (in this case InstallShield AdminStudio).

Hi Packmsi,
A transform, or .mst file, is a Windows Installer file that contains changes to an MSI database to be applied when the MSI package is installed. According to me, If you are editing MSI, then you are corrupting it .

HI ekniranjan,

I got thet .mst file has to be applied with the msi and it contains changes to the MSI file.

My question is that when i edit the msi and save it as msi, u have told that msi will be corrupted.
I want to know waht exactly is corrupted in the msi.

For ex.
My requirement is to change the company name property in the msi.
For this property alone instead of creating a Transform if i edit the msi and save the property, what exactly is corrupted.

You could edit the vendor msi if you like, there is no problem with it, it won't corrupt it

But best practice is to use an mst.

Packmsi,
You should do everything in MST only .................... why means, initially MST itself states that if you want to edit msi create MST, so that will be the final answer. Why means ? try to do that one and see the results ! i never done it.

What I think Annuj may have been driving at is that if you use Wise to save an MSI, it inserts additional tables into the MSI so, whilst not corrupt exactly, it wouldn't be in its virgin state.

Thanks for clear explanation in details VBScab.....................

You need to create a transform and edit vendor msi.Tats the standard procedure. creating a transform is easy too just use tuner.

HI Harshakola,

Thanks for the reply.

My Question is instead of creating a Transform what will happen if i edit the MSI itself and do the necessary changes in MSI and save it as MSI itself.

For Ex. If i have a.msi received from the Vendor and the PIDKEY property needs to be set.
Instead of creating a transform if i edit the a.msi and added the Property PIDKEY and saved it as a.msi itself.

What are the problems if i do like this.Editing the Vendor MSI straightaway?

What are the problems if i do like this.Editing the Vendor MSI straightaway?

In my opinion, the major danger besides losing Vendor Support (updates/ patches/ helpdesk support.. this CAN be a big deal) is that you lose your baseline when working with MSIs
When creating an MST you'll always have that which the vendor has supplied readily available, completely separated from your changes. Something to fall back on so to speak.

When directly adapting vendor MSIs you lose this. There's no way of distinguishing your changes from the original. Agreed, in the case of one license key this is not a big deal. But what if we're talking 10 changes, or 20, or 50? Or what if they say "Put that property back to its default", but you happen to have changed it into something else and don't remember/haven't documented what it used to be and try as you might the original vendor MSI is nowhere to be found anymore...?

PJ