Fix Aspire ServiceDefaults project template naming #31616
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses a template naming issue in the .NET MAUI Aspire Service Defaults project template and adds a test to ensure correct project file naming. When adding this template to your project it would not adopt the project naming, but instead would use the same generic name for each project. This PR fixes that.
Template configuration fixes:
defaultNameandsourceNameintemplate.jsonto use consistent and correct naming conventions for the project template.primaryOutputspath intemplate.jsonto match the expected project file name.Testing improvements:
AspireServiceDefaultsTemplateUsesCorrectProjectNameinSimpleTemplateTest.csto ensure that the template generates the correct project file name for various input names, and that no incorrectly named files are created.Fixes #30365