On Windows Server 2003 Standard Edition, a customer installed .NET 3.5 SP 1. Whenever we run our installer built with InstallShield 2009, the installer complains that the target machine does not have the .NET 3.5 SP 1 dependency. The customer has uninstalled and reinstalled .NET 3.5 SP 1 a couple of times, rebooting each time, but our installer never detects it. The installer, by the way, works fine everywhere else.
To test, we successfully ran one of our apps built with .NET 3.5 SP 1 (it uses LINQ) but does not have an installer. No problems there, so we are confident the correct Framework is installed. We suspect there is something in this machine’s registry that just won’t satisfy InstallShield 2009’s dependency logic. What do we do next?
Are you using the prerequisites from http://kb.acresso.com/selfservice/viewContent.do?externalID=Q200284 or something else? If the prerequisites, it’s easy to open them in the prerequisite editor to identify what registry keys or files they check.