public static class ContentBuildRunnerTurns an imported project into a directory a game or a CDN can be pointed at.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
⚠ The build itself is ContentPipeline's, in Vixen.Editor.Assets, and what is left here is the console. The editor builds content too, and two orchestrations over the same components drift — the way this one would drift is the editor and vixen content build producing different output for one project, which reads as a machine problem for as long as it takes somebody to compare two catalogs by hand.
Fields and properties (2)
public const string HashFileSuffixWhat the build wrote, beside the catalog, so a static host needs nothing else.
public const string CatalogFileNameThe catalog's file name, which is what a runtime and a server both expect.
Methods (2)
public static bool Run(Project project, string target, string outputDirectory, DiagnosticWriter output, bool forServer = false)Plans, packs and writes a content build.
public static void Write(DiagnosticWriter output, ContentDiagnostic diagnostic)Puts one of the pipeline's diagnostics on the console.
Used by (4)
- AddressRunnerVixen.Cli
- DoctorRunnerVixen.Cli
- ImportRunnerVixen.Cli
- VixenCommandVixen.Cli