Wise 7 Bug for 64 bit packaging
Ok, so we are using Wise Package Studio 7 SP3 for packaging on Windows 7 64 bit. Now we were creating a simple package, and I created a new Windows installer package and selected the option of Target Platform (x64). Now as an example, lets say my application installs the following registry :
REGEDIT4
[HKEY_CLASSES_ROOT\.rar\ShellNew]
"FileName"="C:\Program Files\WinRAR\rarnew.dat"
When I import this registry in Wise, C:\Program Files\ should be resolved as [ProgramFiles64folder], but instead it gets resolved to [ProgramFilesFolder], and as a result when I install my MSI, I get the registry value as"C:\Program Files (x86)\WinRAR\rarnew.dat" which is not what it should be.
Also in case you import this registry entry in your MSI:
REGEDIT4
[HKEY_CLASSES_ROOT\.rar\ShellNew]
"FileName"="C:\Program Files (x86)\WinRAR\rarnew.dat"
It gets resoved to [ProgramFilesFolder] x86\, which is again wrong.
Any idea if this is a known bug in WPS 7?
Regards,
Kunal
[HKEY_CLASSES_ROOT\.rar\ShellNew]
"FileName"="C:\Program Files\WinRAR\rarnew.dat"
When I import this registry in Wise, C:\Program Files\ should be resolved as [ProgramFiles64folder], but instead it gets resolved to [ProgramFilesFolder], and as a result when I install my MSI, I get the registry value as
Also in case you import this registry entry in your MSI:
[HKEY_CLASSES_ROOT\.rar\ShellNew]
"FileName"="C:\Program Files (x86)\WinRAR\rarnew.dat"
It gets resoved to [ProgramFilesFolder] x86\, which is again wrong.
Any idea if this is a known bug in WPS 7?
Regards,
Kunal
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
AngelD
14 years ago
Make sure to tick the component holding the .dat file as 64bit (msidbComponentAttributes64bit attribute bit), the destination should still be ProgramFilesFolder.
Posted by:
shh.killer
14 years ago
we had a scenario like :
our application was of 32 bit and the OS which we were deploying the application was 64 bit .
It was required to put the files in program files and not under program files(86).
so i changed the component to 64 bit . so it worked.
like angelid said tmark component is of 64 bit. or in component table we can add component attribute 256.
http://msdn.microsoft.com/en-us/library/aa368007(VS.85).aspx
i don't if this is how it is to be done but it is working.
our application was of 32 bit and the OS which we were deploying the application was 64 bit .
It was required to put the files in program files and not under program files(86).
so i changed the component to 64 bit . so it worked.
like angelid said tmark component is of 64 bit. or in component table we can add component attribute 256.
http://msdn.microsoft.com/en-us/library/aa368007(VS.85).aspx
i don't if this is how it is to be done but it is working.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
