Get Started
dotnet add package nkast.Xna.Framework.Content.Pipeline --version 4.3.9001
| Product | Versions |
|---|---|
| .NET | |
| .NET Standard | |
| Other |
README
Xna.Framework.Content.Pipeline
Asset compilation and processing pipeline for KNI games.
Overview
The Xna.Framework.Content.Pipeline is a development-time package that provides the base infrastructure for compiling game assets into optimized binary formats. It includes:
- Content Processor Framework: Base classes and attributes for processors
- Content Compiler: Asset compilation to binary XNB format with optional compression
- Intermediate Serialization: XML-based intermediate format for asset data
- Type Writers: Binary serialization writers for custom types
- Importers: Base infrastructure for custom asset importers
- Compression Support: LZ4 and Brotli compression codecs
Installation
dotnet add package nkast.Xna.Framework.Content.Pipeline
Quick Start
Create a custom content processor:
using Microsoft.Xna.Framework.Content.Pipeline;
[ContentProcessor(DisplayName = "My Custom Processor")]
public class MyProcessor : ContentProcessor<MyData, ProcessedData>
{
public override ProcessedData Process(MyData input, ContentProcessorContext context)
{
// Transform input data
ProcessedData output = new ProcessedData();
output.ProcessedValue = input.Value * 2;
return output;
}
}
[ContentTypeWriter]
public class ProcessedDataWriter : ContentTypeWriter<ProcessedData>
{
public override void Write(ContentWriter output, ProcessedData value)
{
output.Write(value.ProcessedValue);
}
}
Importers
- XmlImporter: Imports XML-based intermediate format files for asset data
Processors
- PassThroughProcessor: Pass-through processor that outputs input without modification
Downloads by Version
Similar & Alternative Packages
Hand-picked matching NuGet libraries based on tags & ecosystem
Depended On By
Find packages that declare this package as a dependency. NuGet does not provide a reverse-dependency endpoint, so candidates are checked on demand.
Adoption Assessment
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
Compatibility metadata lists 3 target frameworks; confirm the exact target used by your application.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.