Software Deployment Question

wise package studio 5.1

02/01/2010 3326 views
Hello all,

I have installed Wise package studio 5.1 and i need to use the "system requirements" tab.
Its seems that the version mentioned over there are not updated.
I need to update the .Net Framework verison.
How can i update this list?

Thank you very much
0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

I think you may struggle to update the predefined list of System Requirements because it appears that, for example, adding a search for .NET Framework v1.0.3705 (which is an option you should already have) adds the custom action WiseGetDotNetVersion. This is a WISE DLL which probably has a fixed and unmodifiable range of versions of .NET framework it is able to detect.

Instead, you may have to do this as a System Search and specify a launch condition that way. The installed versions of .NET framework already present on a system can be detected by searching on subkeys of the following registry key



Answered 02/01/2010 by: spartacus
Black Belt

Hi again,

Thank you very much for your respond.

My original purpose is to check 2 requirements on the station while installing:
Net framework 3.5
Windows installer 4.5.
If one of the above is not present, to popup a message.

Unfortunately, I do not have much knowledge with Wise package studio.
Can you send me a link to an article that will explain what you wrote earlier?

Thanks again
Answered 02/01/2010 by: amrios
Orange Belt

Handling the minimum version of Windows Installer is the easier of the two requirements to implement in your project.

In Windows Installer Editor select Setup Editor view and click the Product tab, you should see an icon for 'Summary', click that and on the right hand side of the screen, you will see an entry for Minimum Installer Version. You can modify this from the default setting 2.00 (?) to whichever minimum you require.

Once your package is built it will not install on systems having Windows Installer version below the minumum you specified.

Now the next part for .NET Framework 3.5 requirement :-

Select Installation Expert and click on 'System Search'. Click the Add button and select 'Registry'

In the next dialog, fill in the Property field with a name of your choice, for example DOTNET_3_5_FOUND and change the 'Operation' field to 'Read raw value from registry'. Change the Root value to HKEY_LOCAL_MACHINE . Fill in the Key value field with SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5

Finally fill in the Value Name with the word Version

This should then mean that when the package is installed, if .NET 3.5 is found on the target machine, the property DOTNET_3_5_FOUND will contain the actual numeric version of .NET Framework 3.5. If it is not found on the system, the property will be undefined (null).

The last step is to set a launch condition based on the property, so select Setup Editor and the 'Product' tab again, now click the Launch Conditions tab. Right click the white space on the right hand side of the screen and select New .. Launch condition. In the dialog that follows, enter DOT_NET_3_5_FOUND <> "" in the Condition field and your warning text in the Message Text field, for example You must have .NET framework 3.5 to install this package

The above method will look for a specific, rather than minumum requirement for .NET 3.5, but you could add additional System Searches for later versions and alter you launch condition to allow for these as well.

There's help on all this in the Windows Installer Editor help file supplied with Wise Package Studio.
Answered 02/01/2010 by: spartacus
Black Belt

Thank you for all your time

have a nice day

Amir [:)]
Answered 02/01/2010 by: amrios
Orange Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ