Skip to content

Commit f3df5d7

Browse files
authored
Added XNB Format spec doc (#235)
* Added XNB Format spec doc * Add missing file
1 parent b0f48fd commit f3df5d7

File tree

4 files changed

+4
-0
lines changed

4 files changed

+4
-0
lines changed

articles/getting_to_know/whatis/content_pipeline/CP_Architecture.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,8 @@ The managed code objects created by the Content Processor are serialized into a
4040

4141
The format of data in the .XNB file is tightly coupled to the MonoGame Framework. It is not designed for use by other runtime libraries.
4242

43+
If you are intested in the format of the .XNB files you can view the [XNB specification](XNB Format.docx).
44+
4345
### Runtime Components
4446

4547
Runtime components of the Content Pipeline support loading and using the transformed game asset by your MonoGame game. These components use the [MonoGame library](../monogame_class_library/index.md), which can be extended to create custom components.
Binary file not shown.

ci.docfx.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,7 @@
5454
"**/videos/**",
5555
"**/files/**",
5656
"**/snippets/**",
57+
"**/*.docx",
5758
"CNAME"
5859
]
5960
}

docfx.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,7 @@
5454
"**/videos/**",
5555
"**/files/**",
5656
"**/snippets/**",
57+
"**/*.docx",
5758
"CNAME"
5859
]
5960
}

0 commit comments

Comments
 (0)