Open Dragonlaird opened 3 years ago
Actually, it is built in the CsSimConnectInterOp project, but that is an unmanaged C++ project. After building the Solution, CsSimConnect.dll
will be in "./x64/Debug/CsSimConnectInterOp.dll
" or "./x64/Release/CsSimConnectInterOp.dll
".
I had the same issues, had to add the SDK include and lib/static directories manually. The DLL problem I (for now) got around by setting PATH to include the directory where the CsSimConnectInterOp.dll had been put and running CsSimConnectUI.exe manually from the command line... I haven't really use Visual Studio much lately (and especially not for C#), so I couldn't quickly figure out how to modify the PATH that is used while running the app from VS. Probably it is trivial;)
As soon as the functionality starts becoming useful I'l build releases, so you won't have to do the build yourself. Will try to see if I can get a certificate to sign the executables.
Sure, but from my point of view the very point is to build it myself, to be able to debug it, etc, to be able to contribute, and to perhaps eventually incorporate the same ideas in my own code. Do you happen to know whether MSFS WASM modules can also be built from C#, or does it have to be C++? (I actually know C++ better than C# at the moment, as I haven't had to use C# for anything work-related, but I can't say I would prefer C++...)
Sorry to be late in answering this. No, I think that is not possible due to all the dependencies. Remember, the WASM usage by Asobo is only because of the multi-platform aspect: Windows as well as X-Box. Generating WASM would require all the dependencies (NuGet packages used) to be available on the X-Box and some of them are Windows only.
The root cause is that there is not much interest to provide independent alternatives to "standard" Microsoft libraries, of which a large number are Windows-specific.
So, for now, WASM is C++ only.
The form appeared, clicked the sliding button to connect to MSFS2020 and it raised an exception:
I'm not 100% certain of the cause, but I suspect the SimConnect.dll can't be found/used, as it is likely referencing files on your local PC instead of either embedding them in the solution or referencing the required files using, did you use the Environment Variable when specifying the location?