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
- :
- How to add .NET 3.5 Framework Prereq to InstallScript project
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 10, 2008
06:02 AM
How to add .NET 3.5 Framework Prereq to InstallScript project
Hi,
I need to add a prereq for .NET 3.5 Framework to my InstallScript project. I have downloaded the 'Microsoft .NET Framework 3.5.prq' and 'Microsoft .NET Framework 3.5 (Web Download).prq' files from the Accresso website and saved them in my SetupPrerequisites folder. I can open the files fine in my Prereq Editor from InstallShield but they do not show up in my objects list so I can not add to my project.
All I can see in my objects list is the Microsoft .NET Framework Object (I downloaded the most recent version of this object from the Accresso website also). This allows me to set the Framework version to use but 3.5 is not listed as an option (only 1.1, 2.0, and 3.0 are listed).
Any help would be greatly appreciated.
I need to add a prereq for .NET 3.5 Framework to my InstallScript project. I have downloaded the 'Microsoft .NET Framework 3.5.prq' and 'Microsoft .NET Framework 3.5 (Web Download).prq' files from the Accresso website and saved them in my SetupPrerequisites folder. I can open the files fine in my Prereq Editor from InstallShield but they do not show up in my objects list so I can not add to my project.
All I can see in my objects list is the Microsoft .NET Framework Object (I downloaded the most recent version of this object from the Accresso website also). This allows me to set the Framework version to use but 3.5 is not listed as an option (only 1.1, 2.0, and 3.0 are listed).
Any help would be greatly appreciated.
(8) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 10, 2008
11:36 PM
you add the particular .Net setup in your release folder.
Release--->Media-->disk1-->
in that position
and then call that path in your function
like
SRCDIR ^ "VB.net" ^".exe"
Release--->Media-->disk1-->
in that position
and then call that path in your function
like
SRCDIR ^ "VB.net" ^".exe"
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 11, 2008
02:14 AM
John Farkas wrote:
Hi,
I need to add a prereq for .NET 3.5 Framework to my InstallScript project. I have downloaded the 'Microsoft .NET Framework 3.5.prq' and 'Microsoft .NET Framework 3.5 (Web Download).prq' files from the Accresso website and saved them in my SetupPrerequisites folder. I can open the files fine in my Prereq Editor from InstallShield but they do not show up in my objects list so I can not add to my project.
All I can see in my objects list is the Microsoft .NET Framework Object (I downloaded the most recent version of this object from the Accresso website also). This allows me to set the Framework version to use but 3.5 is not listed as an option (only 1.1, 2.0, and 3.0 are listed).
Any help would be greatly appreciated.
you can add your prerequisite as shown in the screenshot attached.. this works fine and you can use it for every setup (exe or msi dosen't matter) which is not included in the list... and you can define also conditions that have to met to avoid installing the Framework on the target if its already exists there and so on..
In Version 2008 of Installshield there is a little bug, which means that the template have to reopen on every new project and then save again to activate
hope this helps
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 11, 2008
08:30 AM
The InstallScript project type does not include support for setup prerequisites. (Therefore, the Objects view in InstallScript projects does not list any setup prerequisites.)
The .NET Framework redistributable is typically added to InstallScript projects through the .NET Framework object. The .NET Framework object that shipped with InstallShield 2008 did not include support for .NET Framework 3.5. (The .NET Framework object that ships with InstallShield 2009 does include support for 3.5.)
You might want to consider customizing the .NET Framework object template that is available for InstallShield 2008; I've never tried it, but I think that you can add support for .NET Framework 3.5 to that template. That would enable you to create an updated .NET object that you could use in InstallShield 2008.
The .NET Framework redistributable is typically added to InstallScript projects through the .NET Framework object. The .NET Framework object that shipped with InstallShield 2008 did not include support for .NET Framework 3.5. (The .NET Framework object that ships with InstallShield 2009 does include support for 3.5.)
You might want to consider customizing the .NET Framework object template that is available for InstallShield 2008; I've never tried it, but I think that you can add support for .NET Framework 3.5 to that template. That would enable you to create an updated .NET object that you could use in InstallShield 2008.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 11, 2008
08:49 AM
DebbieL wrote:
The InstallScript project type does not include support for setup prerequisites. (Therefore, the Objects view in InstallScript projects does not list any setup prerequisites.)
The .NET Framework redistributable is typically added to InstallScript projects through the .NET Framework object. The .NET Framework object that shipped with InstallShield 2008 did not include support for .NET Framework 3.5. (The .NET Framework object that ships with InstallShield 2009 does include support for 3.5.)
You might want to consider customizing the .NET Framework object template that is available for InstallShield 2008; I've never tried it, but I think that you can add support for .NET Framework 3.5 to that template. That would enable you to create an updated .NET object that you could use in InstallShield 2008.
oh i see thanks it was my fault.. my project are all BASIC MSI's
there is it of course possible to add the Framework directly within the PEREQ Editor
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 24, 2008
02:17 PM
DebbieL wrote:
The InstallScript project type does not include support for setup prerequisites. (Therefore, the Objects view in InstallScript projects does not list any setup prerequisites.)
The .NET Framework redistributable is typically added to InstallScript projects through the .NET Framework object. The .NET Framework object that shipped with InstallShield 2008 did not include support for .NET Framework 3.5. (The .NET Framework object that ships with InstallShield 2009 does include support for 3.5.)
You might want to consider customizing the .NET Framework object template that is available for InstallShield 2008; I've never tried it, but I think that you can add support for .NET Framework 3.5 to that template. That would enable you to create an updated .NET object that you could use in InstallShield 2008.
OK, so how do you go about editing this template? And what 3.5 object do we then try to install?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 24, 2008
05:55 PM
First you need to make sure that you have the InstallScript Object for the .NET Framework installed. Then install the object templates. (You can obtain both of those by checking for updates from within InstallShield: Tools > Check for Updates. As an alternative, you can download them from the Acresso Web site: http://www.acresso.com/downloads/downloads_8721.htm.)
When you're done installing the object template, launch the InstallScript Object Customization Wizard. (You can choose to launch it at the end of the template installation, or you can use the shortcut from the Start Menu.) The wizard will walk you through the initial steps. I recommend specifying to create a new object, rather than replace the existing .NET Framework object. The wizard will then create a new object project based on the current object that ships in InstallShield 2008.
You'll need to obtain the .NET Framework redistributable. You can get it from Microsoft's Web site. Add that to the project. Then update the script in the InstallScript view as needed. I think the key event that you'll probably need to update is OnInstalledFile.
When you're done installing the object template, launch the InstallScript Object Customization Wizard. (You can choose to launch it at the end of the template installation, or you can use the shortcut from the Start Menu.) The wizard will walk you through the initial steps. I recommend specifying to create a new object, rather than replace the existing .NET Framework object. The wizard will then create a new object project based on the current object that ships in InstallShield 2008.
You'll need to obtain the .NET Framework redistributable. You can get it from Microsoft's Web site. Add that to the project. Then update the script in the InstallScript view as needed. I think the key event that you'll probably need to update is OnInstalledFile.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 25, 2008
07:56 AM
Please disregard the previous message, it turned out to be a bad download. Redownloading the object templates and reinstalling worked.
I can run the Template Customization app, but it gives another error, see below. The .Net Object is installed, I can add it to a project, so I'm sure its there.
Both VB6 runtime and MFC runtime projects could be started with new objects.
I also tried modifying the .Net object as a last resort, but that choice didn't work either.
Any suggestions?
I can run the Template Customization app, but it gives another error, see below. The .Net Object is installed, I can add it to a project, so I'm sure its there.
Both VB6 runtime and MFC runtime projects could be started with new objects.
I also tried modifying the .Net object as a last resort, but that choice didn't work either.
Any suggestions?