maorray
Posts: 2
Joined: Mon Oct 25, 2010 10:44 am

Advanced installer 7.7 .net 4.0 launch condition

I have sett the launch condition "minimum .net version" to .net framework 4.0.
I have run the installation environment that doesn't have 4.0 framework and it allowed full installation without alerting.

Attached is the installation file.
This is an urgent issue.
Attachments
DBSophic.Qure.WorkloadAnalyzer.Setup.aip
(43.61 KiB) Downloaded 635 times
Bogdan
Posts: 2794
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Advanced installer 7.7 .net 4.0 launch condition

Hello,

This has been tested on our machines and it cannot be reproduced. Is the machine on which you tested the package clean? Also, can you
reproduce this on other clean machines?

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
maorray
Posts: 2
Joined: Mon Oct 25, 2010 10:44 am

Re: Advanced installer 7.7 .net 4.0 launch condition

I simply tested it on a machine that has yet to have .net 4 installed.
The machine itself is simply a server that has nothing else but sql server installed.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Advanced installer 7.7 .net 4.0 launch condition

Hi,

I noticed that you are using multiple builds and the launch condition is set only for "DefaultBuild". Please try setting the launch condition for all builds.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
jbridges
Posts: 38
Joined: Fri Jun 09, 2006 12:36 am

Re: Advanced installer 7.7 .net 4.0 launch condition

I think this is related to a problem I am having. When I upgraded from 7.6 to 7.7, I noticed that if I specify an installer prerequisite of dot net framework 3.5 sp1, in the GUI panel it generates 3 registry entries to check for the install conditions. However, NONE of these appear in the generated .ini file and the installer for the dot net framework does not show at all in the file. It is totally ignored.

I tried two things:
1. removing the cache-folders. This makes it revert to the way it worked for 7.6, but ONLY for some of my projects - not for all.
2. removing the additional registry entries given under the install conditions tab for dot net framework 4.0. That did not work at all for the projects I tried. It still ignored the entry for dot net framework 3.5 sp1. When I say "ignored," I mean it did not appear at all in the .ini file.

I would manually fix this up but I can't figure out how to do it.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Advanced installer 7.7 .net 4.0 launch condition

Hi,

Please note that prerequisite searches are written in the INI only for global prerequisites. Feature-based prerequisites store their information in the MSI.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
jbridges
Posts: 38
Joined: Fri Jun 09, 2006 12:36 am

Re: Advanced installer 7.7 .net 4.0 launch condition

Switching to global option works for me. In previous versions (prior to 7.7) I never had to look at the options tab so this never occurred to me. In the case of dot net framework, I think global should be the default. But now I know what to look for. Thank you.

Return to “Common Problems”