VegaRise.NET

Introduction

VDocs is a fluent, format‑agnostic document framework for .NET. It lets you author a document once with a single, unified DOM, then render that same model as a Word (.docx), PDF, or HTML file — no Microsoft Office installation required.

At the top sits the Vega.VDocs façade: a small, fluent API for building documents (AddParagraph, AddTable, AddImage,AddShape, …) and exporting them (SaveAsWord,SaveAsPdf, SaveAsHTML). Underneath it uses theVega.DOM library, which models pages, sections, paragraphs, runs, tables, images, shapes, styles, and graphics as ordinary .NET classes.

One DOM, multiple formats

Every document you build is a tree of common DOM objects. The same Table,Paragraph, TextStyle, or Gradient you use to build a Word report is what generates the corresponding PDF and HTML output. There is no separate authoring model per format — you only write one document.

Supported outputs

  • • Word (.docx) — via SaveAsWord
  • • PDF — via SaveAsPdf
  • • HTML — via SaveAsHTML or GetHTML

Why VDocs?

  • Fluent API — construct documents in a few readable lines.
  • Single DOM for Word, PDF, and HTML — no format-specific authoring.
  • No Office or Word Interop dependency.
  • Rich layout, styling, tables, images, shapes, gradients, and text effects.
  • Theme, style and language support built in.
  • Well-documented XML comments on every public member.

Where to go next

Most documents only need a handful of the APIs. We recommend reading the Core Content section in order: Paragraphs → Text →Tables → Images → Shapes, then applying styling via the Styles section, and finally exporting. Page Setup and Sections are used when you need custom page dimensions or mixed orientation.

Frequently asked questions

Do I need Microsoft Word installed to use VDocs?

No. VDocs is a pure managed .NET library and does not depend on Word Interop or any Office installation.

Can I build one document and export it to all three formats?

Yes. The same VDocs instance can be exported via SaveAsWord, SaveAsPdf, and SaveAsHTML in any order.

Is the DOM shared across formats?

Yes. Paragraphs, tables, images, styles, colors, and effects are all part of the shared Vega.DOM namespace, so a single document model drives every output.

VegaRiseVDocs.NET

Create Account

Create your VDocs account.

or

Already have an account? Sign in