As reported in #8, the current templates do not support dotnet SDK 8. This is due to how the templates change the Version property in the template's .csproj. I believe the method it used came out of worry about changing a 1.0.0 version somewhere else in the templates.
This PR makes a change to how the version is implemented in all templates. This now uses the more typical "replaces" argument in the parameter symbol, which both simplifies the .json code as well as fixes the issues with using the templates in SDK 8.
This also changes the "target" for replacement from 1.0.0 to {version} in the .csproj, making it much easier to prevent unwanted version replacements.
AlbinoGeek
commented
7 months ago
As reported in #8, the current templates do not support dotnet SDK 8. This is due to how the templates change the
Versionproperty in the template's.csproj. I believe the method it used came out of worry about changing a1.0.0version somewhere else in the templates.This PR makes a change to how the version is implemented in all templates. This now uses the more typical
"replaces"argument in the parameter symbol, which both simplifies the.jsoncode as well as fixes the issues with using the templates in SDK 8.This also changes the "target" for replacement from
1.0.0to{version}in the.csproj, making it much easier to prevent unwanted version replacements.