Skip to content

Feed update process should not move templates forward for out-of-support versions #598

@mattchenderson

Description

@mattchenderson

There are template changes we wish to make for newer versions only. The constraints feature of the dotnet CLI templating engine is insufficient for our needs, and it will cause issues in some clients. As a result, we should just allow the templates to be pinned to the current versions for older TFMs.

Both VS and VS Code separate the templates by TFM, so it should be possible to let these diverge. Technically, that's already the case for the NetCore/NetFx packages which change the HttpTrigger story. The Core Tools is the primary place where there is a gap - we use one package there and rely on a dotnet restore occuring between the project template and item template being scaffolded out. That same behavior could be leveraged here, but we need to confirm that templates will behave as we want if we proceed with that plan.

Additional testing should be performed as part of this work to also confirm that this divergence is properly tolerated by the respective tools.

Beyond that testing, the main work here would be to adjust the Generator tool to ensure it does not take things forward for the older TFMs. We will also need general process changes and account for these in review.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions