• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX/ESP/P3D Single Executable

P

pilotjohn

Messages
32
Country
unitedstates
How is everyone handling SimConnect versioning in their projects? As I understand the FSX SP2 SimConnect DLL and managed assembly libraries work with both ESP and P3D.

This is great, but what happens if someone does not have FSX (and access to the client install) but only P3D or ESP? I just recently tested this, and it fails as it should.

I have a project which was compiled against FSXA SimConnect. Running it on a machine that only ever had P3D installed fails. Since P3D installs the ESP SimConnect client, and since there's no "FlightSimulator" client, the executable fails to load.

Is it possible to require either/or SimConnect clients in a C# project? If so, how? I saw some of the posts about activation contexts, but that just seems cumbersome.
 
I had asked at the P3d forum about versions of SimConnect installed by P3d and got no reply. You've answered my question.

The WindowsSxS folder needs the correct versions of Simconnect for the app you are creating. If you use FSXA and the DLL is missing on the target computer, it won't work

It might be possible to copy the correct SimConnect.dll from your WinSxS folder, and place it in the same folder as the application for distribution. I think the correct version will then be used... kind of defeats the purpose of SxS, but there you go.

Please let me know if that works.

Dick
 
You must log in or register to reply here.
Back
Top