http://bugs.winehq.org/show_bug.cgi?id=21383
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #7 from Anastasius Focht focht@gmx.net 2010-01-16 15:27:12 --- Hello,
--- quite --- How did you see that the installer was looking for .NET. Want to learn how to see those things so I'll not do the same error again. --- quite ---
The queries for .NET's Common Language Runtime (CLR) posted in previous comments are usually an indication that the app/installer wants to use .NET Framework.
--- quote --- fixme:mscoree:GetRequestedRuntimeInfo (L"C:\windows\temp\msi2775.tmp-\Microsoft.Deployment.WindowsInstaller.dll", (null), L"C:\windows\temp\msi2775.tmp-\CustomAction.config", 0x00000000, 0x00000000, 0x33f390, 0x00000104, (nil), 0x33f59c, 0x00000014, (nil)) stub fixme:mscoree:GetCORVersion (0x33f59c, 20, (nil)): semi-stub! --- quote ---
Basically everything with:
mscoree.GetRequestedRuntimeInfo mscoree.GetCORVersion mscoree.CorBindToRuntime(Ex)
There are mixed mode apps, e.g. an unmanaged host with managed components that will result in calls to CorBindToRuntimeHost()/_CorExeMain() that tell the user to install the .NET Framework by printing out messages in console (not the case here).
Also the use of .NET assembly names like "Microsoft.Deployment.WindowsInstaller.dll" indicate managed components which require some version of .NET Framework present.
Other installers use msi product codes or directly query the registry to look for installed .NET versions.
--- For the prerequisite installation of .NET Framework itself refer to appdb. Be aware .NET 3.5 won't install due to blocker bugs.
Regards