Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

C# template.json problem with uppercase name values editortreatas solition #7318

Open
tontoonen opened this issue Nov 27, 2023 · 0 comments
Open

Comments

@tontoonen
Copy link

tontoonen commented Nov 27, 2023

Product

Visual Studio

Describe The Bug

Hi,

We have been setting up template solution with multiple projects.
The approach is that we’re using a template.json config file in the C# Solution.

When we creating a new solution with the template and set the name with uppercase characters
for example: “MyNewSolution”.

An new Solution will be created but all the replacements contains lowercase characters “mynewsolution”, all the uppercase characters are gone.

When we don’t use the option “EditorTreatAs”: “solution” then we get the all the replacements with upper en lowercase characters

To Reproduce

Steps:

  1. Create a new tamplate json
    { "$schema": "http://json.schemastore.org/template", "sln": { "slnFileName": "placeholder_projectname.API.sln" }, "author": "Company", "classifications": [ "WebAPI", "Team X" ], "name": "Team.X.WebAPI.Template", "identity": "Team.X.WebAPI.Template", "shortName": "teamxwebapi", "tags": { "language": "C#", "type": "solution", "editorTreatAs": "solution" }, "sourceName": "placeholder_projectname", "preferNameDirectory": true }
  2. Import new template
  3. Create new project/solution with the new template and set the name with upper and lowercase characters
  4. Project/solution is created and shows lowercase namings

dotnet Info

output

Visual Studio Version

17.7.7

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant