Software Deployment

As per the link, if I am trying to convert 32bit to 64 bit then I have to do below changes.
No, you can't "convert" 32-bit MSI to a 64-bit MSI and you definitely can't "convert" 32-bit application into 64-bit application. 64-bit MSI's are for 64-bit applications. 32-bit MSI's are for 32-bit applications. 64-bit Windows can handle both 32- and 64-bit MSI's just fine.
Whatever crap you're packaging won't turn into diamonds just by changing the wrapping.

Mikko Järvinen

Is it a right way to do it? or is there any better way?
I couldn't quite figure out what you are trying to achieve, but I'd say: No. Yes.
32-bit MSI's work just fine on 64-bit Windows. Only if you have 64-bit application then you'll need 64-bit MSI.
http://msdn.microsoft.com/en-us/library/Aa367430

Mikko Järvinen

http://msdn.microsoft.com/en-us/library/Aa367430

As per the link, if I am trying to convert 32bit to 64 bit then I have to do below changes.
1. In summary information add x64
2. schema=200
3. attribute should be 256

Still in directory "Common Files (64-bit), Program Files (64-bit), or System (64-bit)" do not get added;

Do you understand the difference between 32-bit and 64-bit?

If your 32-bit MSI is going to be run on a 64-bit OS, you need do nothing to the MSI.

A 64-bit MSI contains components designed for a machine running a 64-bit operating system. You don't magically change a DLL or EXE compiled for 32-bit operation to one capable of 64-bit operation just by flagging its component in the MSI as 64-bit. It needs to be compiled as such by the developer.

Whatever crap you're packaging won't turn into diamonds just by changing the wrapping.

MIKKO THERE IS NO NEED FOR THAT TYPE OF LANGUAGE


application packagers of all levels can post whatever questions they like


pointing someone in the right direction is all it takes

Whatever crap you're packaging won't turn into diamonds just by changing the wrapping.
MIKKO THERE IS NO NEED FOR THAT TYPE OF LANGUAGE

Whoops, I meant to say "app" and by diamonds I was referring to 64-bit. Sorry.

Mikko Järvinen

I very well understand 32 and 64 bit apps, as well as differences in msi files which we can see.
When it comes to project standards, then it is always better to study and discussing.
Sometimes we can not convince clients, that 32 bit will work on 64 bit, so we can use the same msi. They want to see seprate packages for both. Thats why, I put this question on forum to confirm, the process which I am using is right or wrong so that I can share this info with my colligues as well.
Thanks for your replies [:)]

Sometimes we can not convince clients, that 32 bit will work on 64 bitFor these clients - where the packager's Baseball Bat proves insufficient - prepare and follow a test plan, agreed with them in advance. Showing screenshots of the app installing and then running in your test environment (possibly using a VM created from their build) should suffice.

ORIGINAL: VBScab

where the packager's Baseball Bat proves insufficient

LOL ! Whenever I experience these type of situations, I REALLY wish if I had one.
@OP - You may like to read the the article written by Darwin Sanoy on 'how-windows-installer-processes-packages-on-64-bit-windows'.