This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- .Net 4 requiremets - which one?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Jun 06, 2010
07:34 PM
.Net 4 requiremets - which one?
i am creating a setup package and i need to reqire the install of .Net 4.0 Client Profile
I see for .Net it is listing the Client profile 2 times
it is also listing full package 2 times
So which one to select?
if one ix for 64 bit and the other one is for 32 bit it does not say which one is which.
I guess i will have to try each of them and figure out what they are...
I see for .Net it is listing the Client profile 2 times
it is also listing full package 2 times
So which one to select?
if one ix for 64 bit and the other one is for 32 bit it does not say which one is which.
I guess i will have to try each of them and figure out what they are...
(7) Replies
‎Jun 09, 2010
02:18 AM
Hi Denny,
Ideally there should be only one entry listed for the Microsoft .NET Framework 4.0 client and Microsoft .NET Framework 4.0 Full Prerequisite.
Kindly ensure that there are no duplicates of these two prerequisites in the location C:\Program Files\InstallShield\2010LE\SetupPrerequisites.
The prerequisites listed in the Redistributables view are based on the .prq (prerequisite) files present in the location C:\Program Files\InstallShield\2010LE\SetupPrerequisites.
Thanks,
Lenwin
Ideally there should be only one entry listed for the Microsoft .NET Framework 4.0 client and Microsoft .NET Framework 4.0 Full Prerequisite.
Kindly ensure that there are no duplicates of these two prerequisites in the location C:\Program Files\InstallShield\2010LE\SetupPrerequisites.
The prerequisites listed in the Redistributables view are based on the .prq (prerequisite) files present in the location C:\Program Files\InstallShield\2010LE\SetupPrerequisites.
Thanks,
Lenwin
‎Jun 09, 2010
08:27 AM
The following .NET Framework 4 prerequisites are available:
Note the following details about these prerequisites:
The .NET Framework 4.0 requires Windows Installer 3.1 or later, as well as the Windows Imaging Component. Therefore, the .NET Framework 4.0 Full prerequisites are configured to have dependencies for the following InstallShield prerequisites:
In addition, the .NET Framework 4.0 Client prerequisites are configured to have dependencies for the following InstallShield prerequisites:
Thus, if you add any of the .NET Framework 4.0 prerequisites to your project, InstallShield also adds prerequisites for Windows Installer and Windows Imaging Component to your installation automatically by default. This could increase the size of your installation.
- Microsoft .NET Framework 4.0 Full
- Microsoft .NET Framework 4.0 Full (Web Download)
- Microsoft .NET Framework 4.0 Client
- Microsoft .NET Framework 4.0 Client (Web Download)
Note the following details about these prerequisites:
- The Full prerequisites install the .NET Framework runtime and associated files that are required to run and develop applications that target the .NET Framework 4.
- The Client prerequisites install the .NET Framework runtime and associated files that are required to run most client applications.
- The two Web download prerequisites require an Internet connection. These prerequisites download the required redistributable files if appropriate. The other two prerequisites are stand-alone installations that do not require an Internet connection.
The .NET Framework 4.0 requires Windows Installer 3.1 or later, as well as the Windows Imaging Component. Therefore, the .NET Framework 4.0 Full prerequisites are configured to have dependencies for the following InstallShield prerequisites:
- Windows Installer 3.1 (x86)
- Windows Imaging Component (x86)
- Windows Installer 3.1 for Windows Server 2003 SP1 (x86)
- Windows Imaging Component (x64)
- Windows Installer 3.1 for Windows Server 2003 SP1 (IA64)
- Windows Installer 3.1 for Windows Server 2003 SP1 (x64)
- Windows Installer 3.1 for Windows XP (x64)
In addition, the .NET Framework 4.0 Client prerequisites are configured to have dependencies for the following InstallShield prerequisites:
- Windows Installer 3.1 (x86)
- Windows Imaging Component (x86)
- Windows Installer 3.1 for Windows Server 2003 SP1 (x86)
- Windows Imaging Component (x64)
- Windows Installer 3.1 for Windows Server 2003 SP1 (x64)
- Windows Installer 3.1 for Windows XP (x64)
Thus, if you add any of the .NET Framework 4.0 prerequisites to your project, InstallShield also adds prerequisites for Windows Installer and Windows Imaging Component to your installation automatically by default. This could increase the size of your installation.
‎Jun 13, 2010
06:35 AM
‎Jun 16, 2010
10:10 PM
MajorWinters wrote:
This is what I see on the requirements screen.
that is what i get...
if one is the web install and the other is not then the text in your gui needs to be fixed so i can tell which is which.
also after installing this install le for VS i get many crashes in VS 2010
even after a full re-install of VS 2010.
WIn7 x64 OS, VS 2010 Premium Ed.
‎Jun 17, 2010
07:08 AM
Hi,
You may choose any one of the .Net 4.0 client package entries under the requirements view.
Both of the .Net 4.0 client package entries perform the same function.
It checks if .Net 4.0 client package is installed on the target system before installing the setup.
The .Net 4.0 full package entry under the requirements view performs the same function.
I am currently working with my engineering team on this issue.
Thanks,
Lenwin
You may choose any one of the .Net 4.0 client package entries under the requirements view.
Both of the .Net 4.0 client package entries perform the same function.
It checks if .Net 4.0 client package is installed on the target system before installing the setup.
The .Net 4.0 full package entry under the requirements view performs the same function.
I am currently working with my engineering team on this issue.
Thanks,
Lenwin