Skip to content

Tagged: MSBuild

All Tags
MSBuild
14pages
3related

MSBuild items, properties and targets that Chirograph reads.

Pages with this tag

Document cache

1

How a URL source keeps its last download, falls back to it when the URL can't be reached, and how committing it and UpdateDocumentCache decide when an API change reaches the client.

How generation runs

2

How Chirograph fetches the generators with PackageDownload, generates into obj, stays incremental, behaves in design-time builds and keeps telemetry off.

Sources

3

Where a client's OpenAPI document comes from, a file, a server project or a URL, and how Chirograph infers which from the item's Include.

Getting started

4

Add the Chirograph SDK to a project, declare a client from an OpenAPI document, register it and call it.

From a file

5

Generate a client from an OpenAPI document kept in the project, as JSON or YAML.

From a server project

6

Generate a client from the OpenAPI document an ASP.NET Core project in the same build writes, including servers with several target frameworks or several documents.

From a URL

7

Generate a client from an OpenAPI document served over HTTP, keep it in a document cache you can commit, and build without the network.

Migrating from LaunchPad's preview

8

The renames from the OpenAPI clients in LaunchPad's MSBuild SDK preview to Chirograph, with the behaviour that changed.

Migrating from OpenApiReference

9

Move a project from Microsoft.Extensions.ApiDescription.Client's OpenApiReference and dotnet openapi, deprecated in .NET 10, to Chirograph's OpenApiClient.

Reference

10

The OpenApiClient item, the properties and target hook, the diagnostic codes and the generated code.

Diagnostics

11

Every error and warning Chirograph raises, CHIRO100 to CHIRO109, with the message, the cause and the fix.

Generated code

12

The files Chirograph writes for each client in obj, which of them are compiled, and the shape of the generated Add<ClientName>() registration and <ClientName>Options.