Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

MSI create in WISE is not detect the framework 4.0 during installation

Updated: 10 Mar 2011 | 4 comments
Mohit Patel's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hello,

         I created a MSI using the Windows Installer Editor. I put the mininum requirement of framework version is 2.0 in the machine in that MSI.

         Now whenever I am going to install that MSI in the machine in which only Framework 4.0 is installed in that machine istallation process is not completed and give me an error message like Framework 2.0 is not Installed in the machine.

         Also I tried the same MSI in the machine in which Framework 3.5 is installed then it works fine.

 

Please help me to solve this issue..

 

Thanks,

Regards

Comments

JohanH's picture
09
Mar
2011
0 Votes 0
Login to vote

Simple. .NET 4.0 is not

Simple. .NET 4.0 is not backwards compatible with older .NET Frameworks. If you need .NET 2.0, you need to install it first. .NET 3.5 is basically backwards compliant and also installs the required components for .NET 3.0 and 2.0.

EdT's picture
09
Mar
2011
0 Votes 0
Login to vote

Although you have not stated

Although you have not stated which version of Wise you are using, I would think it accurate to state that none of the current releases can detect the NET 4 framework explicitly as the DLL that does the detection for the system requirements handling has not been updated since the release of .NET 4.

However, if you explicitly need to test for .NET 4 then there is an MSI property which can help. Here is an extract from MSI.CHM

 

MsiNetAssemblySupport Property

The MsiNetAssemblySupport property indicates whether the computer supports common language run-time assemblies. On systems that support common language run-time assemblies, the installer sets the value of MsiNetAssemblySupport to the file version of Fusion.dll. The installer does not set this property if the operating system does not support common language run-time assemblies. When multiple versions of Fusion.dll are installed side-by-side on the user's computer, this property is set to the latest version of the Fusion.dll file. For example, if .NET Framework version 1.0.3705 (Fusion.dll version 1.0.3705.15)and .NET Framework version 1.1.4322 (Fusion.dll version 1.1.4322.314) are installed side-by-side, the MsiNetAssemblySupport property is set to 1.1.4322.314. For more information, see Assemblies.

In your installation package, check a verbose installation log and look for this property and see what it is set to on your .NET 4 system.

How are you arriving at an operating system that only has .NET 4 on it?  I was under the impression that XP came with .NET 1.x as part of the O/S and later operating systems should have later versions of .NET as standard. Once again, you have failed to mention what O/S you are testing on.  

So when posting in future, please remember to include all relevant information as this helps us to help you

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Mohit Patel's picture
12
Mar
2011
0 Votes 0
Login to vote

Default Framework Installed with OS

Hi,

           Does any one know which version of framework is installed with 64-bit operating system(any OS) with OS package..?

 

Also Framework 2.0 is supports on 64 bit OS platform..?

 

 

Thanking You,

Regards

EdT's picture
11
Mar
2011
0 Votes 0
Login to vote

There is no single answer to

There is no single answer to this, as there are 64 bit versions of XP, Vista and Windows 7, which were brought out at significantly different times and therefore their .NET support is going to vary. The most reliable way to check this is to install the bare operating system and check the version of fusion.dll which is what Windows Installer does when setting the MSINetAssemblySupport property.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.