Skip to content

Commit 1499a6c

Browse files
Merge pull request #17 from mrhelmut/consoles
Added parsing libraries recommendations
2 parents 1c3520c + 3805497 commit 1499a6c

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

articles/preparing_for_consoles.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,12 +55,19 @@ Loading assemblies at runtime with `Assembly.Load()` is not supported.
5555

5656
## Third party libraries
5757

58-
Many third party libraries heavily rely on using reflection or IL emit, this is a common practice for JSON or XML parsers for example.
58+
Many third party libraries heavily rely on using reflection or IL emit, this is a common practice for JSON or XML parsers for example (and they are the most common source of third party incompatibilities).
5959

6060
It is advised to choose very carefully the libraries that you are using when porting to consoles. If you do not select them with this in mind, you might run into a situation in which you will have to rewrite entire chunks of data handling.
6161

6262
The best way to make sure if they will work, is to search if they are **"AOT-compatible"**, or try to compile with the `<EnableTrimAnalyzer>true</EnableTrimAnalyzer>` setting in your `.csproj` and check if there are any warnings related to those libraries.
6363

64+
For example, here are some parsing libraries known for their compliance with AOT compilation and good handling of memrory:
65+
66+
- [TurboXML](https://github.com/xoofx/TurboXml)
67+
- [TinyJSON](https://github.com/zanders3/json)
68+
69+
On the contrary, Newtonsoft JSON is known to be unsupported (there are modified forks around, but we overall recommend to not use it for games).
70+
6471
## Native libraries
6572

6673
If you are using native libraries, make sure that they provide builds for consoles, or make sure that you can compile and run them on consoles yourself.

0 commit comments

Comments
 (0)