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.

Sign up for GitHub

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

Jump to bottom

Migrate old-styled ITEM templates #4563

Open
3 tasks
donJoseLuis opened this issue Apr 6, 2022 · 2 comments
Open
3 tasks

Migrate old-styled ITEM templates #4563

donJoseLuis opened this issue Apr 6, 2022 · 2 comments
Labels
area: Visual Studio The issue is related to Visual Studio New Project Dialog features related to template engine. impeded The issue is impeded by the issue\missing functionality of different product. triaged The issue was evaluated by the triage team, placed on correct area, next action defined.

Comments

@donJoseLuis
Copy link
Contributor

donJoseLuis commented Apr 6, 2022 •
edited by vlada-shubina
Loading

Background

Enable migration of item templates used in Visual Studio based on old template engine and to template.json using constraints.
Other item templates already based on template.json (as MAUI and test templates) should be enhanced to use constraints.

Justification

  • Customer impact - better feature set for authoring comparing to old template engine
  • Engineering impact - no need to support item templates built on 2 different template engines

Work list

  • MAUI templates
  • dotnet test templates
  • old style item templates
@donJoseLuis donJoseLuis added User Story A single user-facing feature. Can be grouped under an epic. Priority:1 Work that is critical for the release, but we could probably ship without Cost:M Work that requires one engineer up to 2 weeks 7.0 triaged The issue was evaluated by the triage team, placed on correct area, next action defined. labels Apr 6, 2022
@donJoseLuis donJoseLuis mentioned this issue Apr 6, 2022
Closed
2 tasks
This was referenced Apr 7, 2022
Closed
Closed
@JanKrivanek
Copy link
Member

Prerequisity: dotnet/sdk#28915

@YuliiaKovalova YuliiaKovalova removed Priority:1 Work that is critical for the release, but we could probably ship without Cost:M Work that requires one engineer up to 2 weeks 7.0 labels May 18, 2023
@vlada-shubina
Copy link
Member

vlada-shubina commented May 18, 2023 •
edited
Loading

This is not yet done. After implementing support of evaluating context for item templates in #4285, the next prerequisite is to align with VS team for broader support of item templates, including 3rd party templates. VS needs more metadata then dotnet new here, including hierarchy paths in Add new item dialog and default extension. This may be potentially implemented in ide.host.json.

Then we can start to advise teams to do the migration.

@vlada-shubina vlada-shubina added area: Visual Studio The issue is related to Visual Studio New Project Dialog features related to template engine. impeded The issue is impeded by the issue\missing functionality of different product. and removed User Story A single user-facing feature. Can be grouped under an epic. labels May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: Visual Studio The issue is related to Visual Studio New Project Dialog features related to template engine. impeded The issue is impeded by the issue\missing functionality of different product. triaged The issue was evaluated by the triage team, placed on correct area, next action defined.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@JanKrivanek @vlada-shubina @donJoseLuis @YuliiaKovalova