Editing msi's on Win7 x64 but target OS is x86
Hi All!
Does anyone know if it's safe to edit my msi's and mst's (basic msi editing and making transforms) on a x64 Win7 installation while developing for target OS Win7 x86 with Adminstudio 2010? Unlike WPS I have little experience with Adminstudio.
I have a VM (Win7 x86) with only the repackager on it for all the repackaging stuff, but now I'm wondering if I can use my host-pc (x64) for the full installation of Adminstudio.
Especially I want to know if Adminstudio leaves any (OS)footprints in the msi's and transforms I will make. If it does, I can better make an extra VM with the full Adminstudio on Win7 x86.
Hopefully you understand my question. [;)]
Regards,
Peter
Does anyone know if it's safe to edit my msi's and mst's (basic msi editing and making transforms) on a x64 Win7 installation while developing for target OS Win7 x86 with Adminstudio 2010? Unlike WPS I have little experience with Adminstudio.
I have a VM (Win7 x86) with only the repackager on it for all the repackaging stuff, but now I'm wondering if I can use my host-pc (x64) for the full installation of Adminstudio.
Especially I want to know if Adminstudio leaves any (OS)footprints in the msi's and transforms I will make. If it does, I can better make an extra VM with the full Adminstudio on Win7 x86.
Hopefully you understand my question. [;)]
Regards,
Peter
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
package_aligator
13 years ago
The OS on which you compile the .msi and the target system for which the msi is intended aren't dependent, no footprints are inserted.
The msi type(32-bit or 64-bit) is chosen by selecting "Platform" drop-down list from Summary Information and choosing the processor architecture.
Further, depending on the msi type, the Windows Installer service will redirect all data (files,registries,etc.) to corresponding location, for example a 32-bit msi will be installed in "C:\Program Files (x86)" while a 64-bit one will go to "C:\Program Files".
The msi type(32-bit or 64-bit) is chosen by selecting "Platform" drop-down list from Summary Information and choosing the processor architecture.
Further, depending on the msi type, the Windows Installer service will redirect all data (files,registries,etc.) to corresponding location, for example a 32-bit msi will be installed in "C:\Program Files (x86)" while a 64-bit one will go to "C:\Program Files".
Posted by:
pjbaars
13 years ago
Thanks for the quick reply!
So I assume it's safe to do that. This removes the need for an extra VM.
Thanks!!
Regards,
Peter
So I assume it's safe to do that. This removes the need for an extra VM.
Thanks!!
Regards,
Peter
Posted by:
anonymous_9363
13 years ago
For editing existing MSIs, it wouldn't make a difference. I think the generally accepted wisdom for re-packaging (for clarity, I mean turning a legacy installer into an MSI) is that you do so on a 32-bit system.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.