MGCB Content Pipeline: Cache Invalidation during Global Property Changes
0 reputation · 19 Sept 2023, 16:53 UTC
The MonoGame Content Builder (MGCB) utilizes a build-cache system to optimize the compilation of assets into platform-specific .xnb binary files. This mechanism typically triggers a rebuild when a source asset's timestamp changes.
However, there is uncertainty regarding how the pipeline handles changes to global build properties within the .mgcb project file. If a global configuration is modified but the individual source assets remain untouched, the cache may not automatically invalidate, potentially leading to stale binary outputs that do not reflect the updated global settings.
Technical Constraints
- Targeting MonoGame 3.8+ using the dotnet tool
mgcb-editor. - Reliance on the XML-based project definition for build parameters.
Does the MGCB pipeline track global project property changes as a trigger for asset re-processing? If not, what is the recommended method to ensure all assets are synchronized with global configuration changes without performing a full manual Clean operation?
monogame