Summary
XNA had it easy, a single platform/api and using TitleContainer or StorageContainer to access runtime content not loaded through the Content Pipeline.
However, things are different in the multi-platform world with various limitations or paths for accessing file systems and the recommended guides are not really there to walk through it all.
Requirement
We need a guide that pulls all the relevant information for best practice that covers all platforms, and any peculiarities/considerations a platform might have (bundles for iOS/Android for instance).
It needs to cover:
- System.IO
- TitleContainer
- StorageContainer (when it is available again)
- ??
As well as information specific to a platform if there are special considerations.
- Android
- iOS
- Windows (and handhelds)
- Xbox (public guidance only, non-nda info)
- Playstation (public guidance only, non-nda info)
- Switch (public guidance only, non-nda info)
And any future hardware platforms that MonoGame supports.
Summary
XNA had it easy, a single platform/api and using TitleContainer or StorageContainer to access runtime content not loaded through the Content Pipeline.
However, things are different in the multi-platform world with various limitations or paths for accessing file systems and the recommended guides are not really there to walk through it all.
Requirement
We need a guide that pulls all the relevant information for best practice that covers all platforms, and any peculiarities/considerations a platform might have (bundles for iOS/Android for instance).
It needs to cover:
As well as information specific to a platform if there are special considerations.
And any future hardware platforms that MonoGame supports.