It would be beneficial to include all of your NuGet package code within this repository.

[padfoot044]

Includes the full source code of the NuGet package in this repository to streamline development and management.

[KyleMcMaster]

@padfoot044 Thanks for opening the issue! In order to help maintainers understand your needs, can you clarify which NuGet packages you would like to see included? Can you elaborate on how that would benefit this repo as it is a template?

I'm curious as to what problem this solves since dotnet templates do not include package sources for example. A dotnet new worker project doesn't ship with the source for Microsoft.Extensions.Hosting, so I'd like to see the benefit for including any referenced packages as part of this repo.

[padfoot044]

@KyleMcMaster Thanks for the question. To clarify, I’m not suggesting vendoring third-party NuGet dependencies. This is specifically about NuGet packages that are authored and maintained by this project.

Including those package sources in the same repo would make it easier to develop, debug, and evolve the template and its related packages together, reduce contributor friction, and keep version alignment explicit. External packages (e.g. Microsoft.Extensions.*) would of course remain referenced normally.

Happy to discuss alternative approaches if there’s a better pattern for this use case.

[padfoot044]

Example

[ardalis]

None of those are are maintained by this project.

[wbunthof]

@padfoot044 All the nice packages from Ardalis can be found as repositories from him. You can look the up via: Ardalis Repositories. So they are each in a seperate repository, so they are handled similar to external referenced packages but then from Ardalis.