If you want to build Aspire.Hosting packages to share with the community is there a package naming convention?

[baynezy]

I have an Aspire package that I am working on that I want to share with the community. I won't be able to follow the Aspire.Hosting.* package naming convention as that namespace is reserved on NuGet.

So, is there an agreed-upon pattern for third parties to create packages that will aid discoverability?

[davidfowl]

Good question! We don't have any guidance for the package name itself and it varies. We've been discussing a new package tag to let others opt into the tooling that will detect aspire compatible packages though.

PS: This doc is a good read when you are writing hosting packages https://github.com/dotnet/aspire/blob/main/docs/specs/appmodel.md

[baynezy]

Thanks @davidfowl . Is there a GitHub issue I can follow for the package tag?