You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have some limited installations of Office which do not include Outlook. In this case, the 32 bit XLL is incorrectly registered, because the "bitness" registry entry for Outlook is used to determine if 32 or 64 bit should be used:
This is some years late, but someone else might ask.
In the Product.wxs in the CustomAction.cs file goto the GetAddInName function and add a check for the registry key
"Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration\Platform"
This will have the platform in here too, might solve your issue.
eg.
// Check click to run installs for bitness first, just incase Outlook is not installedRegistryKeyclickToRunPlatform= localMachineRegistry.OpenSubKey(@"SOFTWARE\Microsoft\Office\ClickToRun\Configuration",false);if(clickToRunPlatform!=null){objectplatformValue= clickToRunPlatform.GetValue("Platform");if(platformValue!=null){if(platformValue.ToString()=="x64"){returnszXll64Name;// Exit early since platform is x64}}}
Failing this, you could try getting the binary type of excel application its self, you can also find the binary path of excel in registry in here "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths"
eg
privateconstushortSCS_32BIT_BINARY=0;privateconstushortSCS_64BIT_BINARY=6;[DllImport("kernel32.dll")]privatestaticexternboolGetBinaryType(stringlpApplicationName,outushortlpBinaryType);privatestaticushortGetBinaryType(stringfilePath){if(!GetBinaryType(filePath,outushort result))thrownew Exception("Error while calling GetBinaryType");returnresult;}
We have some limited installations of Office which do not include Outlook. In this case, the 32 bit XLL is incorrectly registered, because the "bitness" registry entry for Outlook is used to determine if 32 or 64 bit should be used:
WiXInstaller/Source/InstallerCA/CustomAction.cs
Line 278 in 330c97f
The text was updated successfully, but these errors were encountered: