Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.
Use this section for document-level SVG workflows that go beyond basic loading, editing, and single-file conversion. Learn how to merge multiple SVG files into one PDF, XPS, PNG, JPG, or other output file, optimize SVG documents for cleaner output, and configure runtime, theme, and network services in Aspose.SVG for .NET.
SVG document workflows often combine several API areas: document loading, rendering, resource handling, optimization, and environment configuration. Start with the article that matches your document-level task.
| API | What it helps with |
|---|---|
| SVGDocument | Load SVG sources, inspect or edit documents, and pass documents into save or rendering workflows |
| SvgRenderer | Render one or more SVG documents to an output device |
| PdfDevice | Write rendered SVG content to PDF output |
| ImageDevice | Write rendered SVG content to PNG, JPG, BMP, TIFF, or GIF output |
| SVGOptimizer | Optimize SVG markup according to selected optimization options |
| Configuration | Configure runtime services used when documents are loaded, resolved, or rendered |
An SVG document workflow is a multi-step task that works with the whole SVG document, such as merging files, optimizing markup, resolving resources, or configuring how an application loads and renders SVG content.
Yes, in Aspose.SVG for .NET this workflow is closely related to rendering and conversion. It takes multiple SVG input files and produces one output file such as PDF, XPS, PNG, JPG, BMP, TIFF, or GIF. It is not intended to create one combined editable SVG document.
Configure the environment when your application needs custom resource loading, network behavior, runtime services, user-agent settings, or theme handling before documents are loaded or rendered.
Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.