So it may be a case of creating another project file for your chosen platform.
see the "#if WINDOWS_STOREAPP" in atlas.cs - required because windows store apps have to load assets in a different way to other. The only other thing that I've also done is use compilation directives to get round platform specific issues - e.g. Thus the project files have any platform specific information in them but use the same source code. If you want to target a different platform (e.g android, or windows (non store app), or mac or playstation or whatever then it would probably be a case of just making another project in the same way.
#XAMARIN VISUAL STUDIO SKELETON UPDATE#
Everytime an update to the runtimes is released then I just update these two project files with links to the new source files and then issue a pull request. If you look at the folders for these two projects then you'll notice that there are no source files in the folders - this is because they 'link' directly to the source code in the c# and xna folders - thus no need to copy files around and have to worry about keeping them synchronised.
If you are targeting iOS (using Xamarin studio on the mac) or a windows 8 store app then there are two spine run-time projects already set-up to do this in the "spine-monogame" folder within the spine runtimes repository. What platforms are you initially targeting? Interestingly though, taking this approach did not fix your original repository - so there must be something different about the spine-runtime that you built in the original repository. I put these in the LoadContent immediately after the UpdateWorldTransform() I also added the following two lines to ensure that spineboy appeared in the middle of the screen. For more information about these prerequisites, see Installing Xamarin.For information about connecting Visual Studio 2019 to a Mac build host, see Pair to Mac for Xamarin. (optional) A paired Mac to build the application on iOS. The problem before was that they weren't being copied and hence could not load. Visual Studio 2019 (latest release), with the Mobile development with. This then means that the files are copied as part of the output/deployment along with the exe and dlls.