The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click
here
for more information.
The attached InstallScript LogSystemInfo function uses the Kernel32.GetProductInfo function to determine the Windows product type (e.g. home, professional, enterprise, ultimate, ... Windows editions).Note that the code calls a custom WriteLogLine at ...
You could also install the TFS Build Service on a 32-bit Windows edition. I'm pretty sure that the InstallShield Automation interface will work via a 32bit TFS build engine.http://msdn.microsoft.com/en-us/library/dd578619.aspx
The problem is that ISWiAutomation17.dll is a 32-bit assembly, and the TFS build agents are 64-bit processes. So even though the "MSBuild Platform" parameter is set to X86, the parent process which actually uses the BuildTasks.dll still runs as a 64...
Same issue on x64 editions of Vista and Windows 7 (and I guess on all x64 OS). For InstallScript installations the solutions is to add the following code before the call to the AddFolderIcon function.if (SYSINFO.bIsWow64) then StrReplace ( szIconPa...
