Release 5.3.1

[matthid]

No description provided.

[matthid]

SemVer is missing

[kblohm]

My first idea was also to change the version inside the script, but i dont think it is needed unless you want to always install pre-releases.
I just tested installing the global tool without the --version parameter and that does install 5.3.0.
You can not leave the version blank for the DotNetCliToolReference, but as far as i can tell, using a * here also resolves to 5.3.0.

Just gotta love nuget and their lowest-version policy ;).

[matthid]

• here also resolves to 5.3.0.

apparently * resolves to 5.0.0 as well... what a mess. What is wildcard even good for...

[kblohm]

Are you sure it does?
If i specify <DotNetCliToolReference Include="dotnet-fake" Version="5.0.0" /> and then run

dotnet fake --version

in that folder, i get a 5.0.0.
If i change that to * i get 5.3.0.

[matthid]

@kblohm I meant dotnet tool install --version *, yes CliToolReference seems to behave kind of reasonable

[kblohm]

For the global tool, just do not specify a --version at all. Thats what i meant for the global one.

[kblohm]

Also very nice that both of these behave differently xD

[matthid]

Welcome to the world of nuget.

Yes my "fix" is still kind of broken, if we want to install latest....

[kblohm]

If you want, i can change the template to only add the version when it is specified and use
<DotNetCliToolReference Include="dotnet-fake" Version="*" /> / not add the --version otherwise.

[matthid]

I'm not really familiar with the template thing and how to switch between given and not-given version flag. Additionally, CliToolReference is basically obsolete already

[kblohm]

Well i would say it is obsolete when they have a solution to properly install the global tools for projects.
If you have a minute, you can look at #2055.