Building 64-bit Windows Installer Packages Using Wise Package Studio
Filed under:
Wise Package Studio
Basics
Submitted by WiseUser on Wed, 2008-05-07 10:17.
A 64-bit package consists partially or entirely of 64-bit Windows Installer components.
The following is required for every 64-bit Windows Installer package:
- The value "Intel64" must be entered in the platform field of the Template Summary property if and only if the package will run on an Intel64 processor.
- The value "AMD64" must be entered in the platform field of the Template Summary property if and only if the package will run on an AMD64 processor.
- The Page Count Summary property must be set to the integer 200 because Windows Installer version 2.0 is the minimum version capable of installing 64-bit components.
- Each 64-bit Windows Installer component in the package must include the msidbComponentAttributes64bit bit in the Attributes column of the Component table.
(41 votes)
- Login or register to post comments
- 878 reads
- Printer-friendly version
Need more info..
Gooood Start to discuss on the 64 bit appz packaging.
Wiseuser, can you please give us more overview and other key techniques of 64Bit App packaging?
Cheers'
Vijay
Support Link for buildin 64 bit windows installer
http://blogs.msdn.com/heaths/archive/2005/10/24/wi...
Wiseuser
Altiris Certified Professional
Some more Information on building 64 bit apps
In general , 32 and 64 bit Microsoft Installer (MSI) packages are treated in the same way except for how Windows Installer treats folder variables such as [Program Files] and [System Folder] , and how it writes components into the registry or GAC.
When you create a 32- or 64-bit MSI package, the processor architecture is noted in the .NET Framework assembly's strong name identity when it is installed in the GAC . You can also create setup projects for 64-bit computers from 32-bit computers .
64-bit MSI packages can support both 32- and 64-bit DLLs or EXEs to perform custom actions ; however , 32-bit MSI packages cannot support 64-bit DLLs or EXEs to perform custom actions.
Whenever you add a file or assembly to a merge module project, it is scanned to determine whether it is a 32- or 64-bit target platform. This is done in order to ensure that your 64-bit merge modules do not contain a mix of 32- and 64-bit code.
If the merge module contains a 32-bit file, Visual Studio will notify you with a message and will not add the file. If you add a managed assembly marked as 32-bit only, you will get build warnings, but the file or assembly will be included in the target installation
Wiseuser
Altiris Certified Professional
Wise package studio
Is there anything that has to be installed/ enabled for me to start creating 64 bit installs? I have it installed on a 64 bit box.
Under project Details, the only option i get for target platform is Intel 32-bit.
other than that creating 64 bit packages shoudl be roughly the same as 32 bit ones right?