Makes no difference how many you have, only what apps use them and how they use them.

Ok, sounds good as we previously were thinking having multiple versions installed could cause issues.

How many versions of simconnect.dll for Prepar3d are installed in the C:\Windows\winsxs folder?

Nice topic, I'm having some crashes here and the log shows SimConnect

 

mgh, just checked here and I have 4 simconnect.dll inside \winsxs inside x86_microsoft.esp.simconnect, x86_microsoft.flightsimulator.simconnect and it seems I have 4 different versions

 

1.0.20.0 (*ESP)

10.0.61259.0 (*flightsimulator)

10.0.61242.0 (*flightsimulator)

10.0.60905.0 (*flightsimulator)

 

And I don't have FSX installed in my machine +1 year and a half

Makes no difference how many you have, only what apps use them and how they use them.

 

Yes ... some applications can dynamically load (LoadLibrary - dynamic binding) and not necessarily just referenced.  Now I doubt many devs use LoadLibrary approach as it's much easier to go the referenced route and expect their referenced version to be installed on the client/user PC.  But devs have been very creative and even use ReadProcessMemory and WriteProcessMemory so who knows the extent of their creativity when it comes to SimConnect.

 

Personally I would use the managed SimConnect.dll and deploy it with my product, avoid the entire issue of client installs ... I've done this many times on managed DLLs without issue.  

 

Cheers, Rob. 

The numbers you give are those in the winsxs folder names which are FSX. What are the corresponding simconnect.dll file version. Mine for FSX are attached. I don't have access to my Prepard pc.

10.0.61259.0     10.0.61637.0

10.0.61242.0    10.0.61355.0

10.0.60905.0  10.0.60905.0