Skip to content

Overhaul project resource guidance for ProjectResource v2 (AddDotnetProject) #2179

Open

Description

In Aspire 17.0, AddCSharpApp / addCSharpApp is marked [Obsolete] (reports CS0618, retiring ASPIRECSHARPAPPS001) and AddDotnetProject / addDotnetProject from Aspire.Hosting.Dotnet (DotnetProjectResource) is the replacement path-based API.

The docs need a coordinated overhaul to make the ProjectResource v2 model the primary guidance instead of piecemeal notes, split out of #2176.

Scope

  • integrations/dotnet/project-resources.mdx — reframe AddProject vs. AddCSharpApp around AddDotnetProject.
  • integrations/dotnet/csharp-file-based-apps.mdx — make AddDotnetProject primary; keep AddCSharpApp only in a migration section.
  • integrations/frameworks/dotnet/dotnet-host.mdx — migration pointer.
  • get-started/add-aspire-existing-app.mdx — file-based AppHost example uses AddDotnetProject.
  • whats-new/aspire-17.mdx — AddCSharpApp obsoletion breaking change.
  • diagnostics/aspirecsharpapps001.mdx — link to migration guidance once it exists (after Consolidate 17.0 retired experimental diagnostics docs #2176 merges).
  • Audit other pages that still use AddCSharpApp or ASPIRECSHARPAPPS001 suppressions.

Publishing

AddDotnetProject configures .NET program publishing automatically. The documentation should describe the supported publishing behavior.

References: microsoft/aspire#20825; publishing configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions