Has this anomaly ever been solved? I am currently seeing this behavior with InstallShield 2012 Professional on a target Windows XP Pro SP2 clean machine (VM) with only .NET 2.0 SP2 installed.My Basic MSI project selects the Microsoft .NET Framework ...