However, the files are not corrupt and provided I remove the Addon entry from the dll.xml file, then FSX runs all other programs/addons without issue. The error message for both files is 'Switch from current encoding to specified encoding not supported'. After many goes trying different approaches I now have FSX running with the Addon entry in the dll.xml file.
This problem doesn't have anything to do with our installers. It has been discussed here already, and it was found the original cause of the XML file corruption was ASN, as reported by an user in this thread:
http://www.fsdreamteam.com/forum/index.php/topic,11834.msg90536.html#msg90536The issue seems to have been reported to ASN developers, so they FIXED their product in the latest Beta, so it won't change the XML file encoding in the wrong way anymore.
However I get an error message saying there is a problem with the 'bglmanx.dll file. Choosing to run it crashes FSX. There is a second message saying: The procedure entry point SimConnect_Text could not be located in the dynamic link library Simconnect.dll. I presume that this is because the Stand Alone Addon Manager program cannot install files correctly, due the above corrupt file problem.
The 2nd message doesn't come from any of our products, it LOOKS like a message from FSUIPC, because it's known to dynamically link for specific procedures in the Simconnect.dll
If FSUIPC cannot find functions in the Simconnect.dll, it means you have a SERIOUS problem with Simconnect, which is the CAUSE of the issues with the Addon Manager, not the other way around. Your issue with the XML files was just an additional issue, which can be easily fixed, but not the main one.
So, your real problem doesn't seem to have anything to do with any of our products, which instead are AFFECTED by a problem with your FSX install, an issue with Simconnect, which seems to be affecting BOTH our modules AND FSUIPC. Note that, none of our modules use, requires or interact with FSUIPC, just the Simconnect issue is affecting both, since they both obviously need Simconnect to work.
You can TRY an FSX SP2 "Repair" (NOT REINSTALL) option, that will hopefully fix Simconnect.