Ah, of course. I forgot about all the extra trickery that FSUIPC has to do.
In my application I bundle separate manifests for the RTM, SP1 and SP2 versions of SimConnect and attempt to create activation contexts at runtime until one of them works. It's really a wonder how Microsoft has managed to make DLL loading so overly-complicated with WinSxS.
That's interesting. I've never used Prepar3D, but I know people successfully use my application with it. I always assumed it installed the FSX versions of SimConnect, but I guess everyone who has it working just has the original FSX installed alongside it. How is SimConnect distributed with P3D if not as a DLL? Is it a static library?
Hm. This does have the advantage of being able to locate all the available versions at runtime, but it does feel a little hacky.. It would be nice if there was some official way of enumerating the available WinSxS DLLs, but I've not been able to find any.
Chris