Botched .Net Framework Install

[dmrdrexel]

So, we upgraded our application and install from .Net Framework 4.0 to 4.5 and upgraded installaware from 15 to 18 at the same time and we ended up creating an installer that installed the 32 bit version of the .Net Framework onto x64 systems. In order to fix the roughly 200 machines that this install has been used on so far we have to tell our customers to use the .Net Clean-up utility to uninstall the botched .Net Framework before installing with the new installer.
2 things:
1) Is there a way to fix this issue on our client's computers via InstallAware so that they don't have to run a cleanup script on their machines?
2) InstallAware does not check the system setting windows in 64 bit mode before installing 32 bit .net and vice versa by default; is this a bug?

Thanks,
Dave

[FrancescoT]

Dear Dave,

1) Is there a way to fix this issue on our client's computers via InstallAware so that they don't have to run a cleanup script on their machines?

I suppose you can easily integrate the cleanup script with you installer. For what I know the tool can be even executed in Unattended mode.
For this purpose you could use the "Run Program" command within the "[DEFINE REGION: Install Application Pre-Requisites]" of your main script and more specifically, within the "if Variable NEEDSUPGRADE Equals TRUE" conditional evaluation. In this way the cleanup script will be executed only, if a previous version of your product is installed on the target machine.

To include the tool with your installer, add it to the Support Files and then access to it at runtime using the SUPPORTDIR pre-defined script variable.

2) InstallAware does not check the system setting windows in 64 bit mode before installing 32 bit .net and vice versa by default; is this a bug?

All our Application runtimes are based on the official Runtime package distributed by the vendor and consequently, it should be the the official Runtime package itself, capable to check if its installation can be effectively executed on a particular target. Anyway, with our latest Runtime packages, we have already added an additional check in order to verify it.

Regards

[dmrdrexel]

Thank you for your help. I would like to be able to run the cleanup script on only on machines that have the issue since it is a dirty last resort and not recommended. I don't want to do more damage than has already been done.

With that being said. Is there a way in the MSI code that I can detect if a 64 bit machine has 32 bit .NET Framework 4.5 installed?

The current method I am trying is to test the registry key HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Version does not seem to work. I looked in the registry and the installer does not appear to be populating that key on 64 bit machine with the bad 32 bit 4.5 framework.

Thanks,
Dave

[FrancescoT]

Dear Dave,

With that being said. Is there a way in the MSI code that I can detect if a 64 bit machine has 32 bit .NET Framework 4.5 installed?

For what I know to see which versions are installed, view the %WINDIR%\Microsoft.NET\Framework directory. (You should also view the Framework64 directory on a 64-bit computer, which can have 32 or 64-bit versions installed.)

http://msdn.microsoft.com/en-us/library/vstudio/y549e41e(v=vs.100).aspx

Regards