Transforms not applying

[Anonymous]

Hello,

I am attempting the transform the msi for the en-us NAVFREE_LP.msi per our standards and the transform does not apply. The only items being modified are Summary Stream information and properties identifying them as being installed by our company.

Has anyone had issue's with transforming the language packs, this is for Freedom Viewer 2018. Any tips would be highly appreciated.

Thanks,

Frank V. 

[m_latz]

How do you try to apply the transformation ?

Can you show us how you pass the transform to the msi ?

regards

Markus

[Anonymous]

Hello Markus,

First I added my edits to the transform that was created with the deployment. So, I'm using the original transform Freedom.mst.

We are using the boot strap to keep the installation as native as possible.

When I noticed that the language pack was installing without my edits, I added the following to the .ini:

[FREEDOM_LANGPACK]
PLATFORM=x64
EXE_PATH=x64\%lang%\NAVFREE\NAVFREE_LP.msi
EXE_PARAM=ALLUSERS=1 TRANSFORMS=D:\Temp\FreedomViewer2018v150131436\Img\x64\en-us\NAVFREE\Freedom.mst
PRODUCT_NAME=Autodesk® Navisworks® Freedom 2018 Language Pack
ADMIN_INSTALL=YES
CONFIG_TRANSFORM=Freedom.mst
TRANSFORMS=Freedom.mst
UPI2_GENERATE=YES
UPI2_PRODUCTLINE=NAVFREE
UPI2_RELEASE=2018
UPI2_UNITTYPE=LP
UPI1_MASTER_ID=ENU64
UPI2_ROOTFEATURE=Uninstall

Maybe there is an issue with my syntax, I've attached the .ini and the language pack install log if it will help.

renamed the ini to .log, please change .ini if you need to look at it.

Any help with this would be highly appreciated.

Thank you,

Frank V.

[m_latz]

What I see is, that you have multiple TRANSFORMS in the same section, so I'm not sure what happens ...

And when I take a look to your log file the transform is not used.

But because each setup is different from Autodesk I have to check this ....

Takes a while ....

regards

Markus

[Mark.Lancaster]

Granted you are slightly above my level of expertise.. 

But from my experience..  The free viewers offered by Autodesk don't allow for your own customization.  Its installed only one way.  Anyhow my 2 cents..

[Anonymous]

Hello,

Digging a little deeper we see that the setup is extracting a totally different transfer and using that which explains why mine isn't being applied.

Can this be disabled so the transform in the target folder is the one that gets a applied, or can the mechanism that created that transform be modified.

Frank V.

[m_latz]

Okay worked.

What I did:

I called the setup.exe and created a deployment. This creates a transformation in the folder ".\img\x64\NAVFREE" with the name freedom-<deploy-name>.mst.

This transformation is applied to both msi's (freedom.msi and NAVFREE_LP.msi)

So I modified this existing freedom-NaviFree2018Mui.mst and my modifications are applied to both msi files.

If you have modifications that should only applied to freedom.msi or NAVFREE_LP.msi use a custom action with a condition.

This method is a bit different from using the ini file to apply your own transformation, but the result is the same.

You can apply all modifications you want !

regards

Markus

[Anonymous]

Hello Markus,

This is awesome and thanks for all your efforts!

When you say existing   "freedom-NaviFree2018Mui.mst", is that the transform that gets created by the Deployment in the Img\x64\NAVFREE.

Again, Thanks,

Frank V.

[m_latz · Accepted solution]

Yes, this is the transformation that the "deployment wizard" creates (my deployment name was "NaviFree2018Mui").

And I used that to modify.

And this transformations is later applied as "_la88AA.tmp.mst" (just a temporary cryptic name) to NAVFREE_LP.msi

The point is that you have one transformations that is applied to both msi packages. And the transformations is located in the same folder as freedom.msi

regards

Markus

[Anonymous]

Again Thank you for your efforts!