[Bug] 6.0 Beta 4 gitversion.msbuild with dotnet build

[christophwille]

When I add 6.0-b4 msbuild nuget, it works fine in VS. When executing dotnet build on the command line it fails when executing

dotnet --roll-forward Major "C:\Users\chwille\.nuget\packages\gitversion.msbuild\6.0.0-beta.4\tools\/gitversion.dll" "C:\Workspace\src\myProject" -output file -outputfile obj\gitversion.json

(exit code 1)

When I run this separately (in the same directory as dotnet build) I get

Could not execute because the specified command or file was not found.
Possible reasons for this include:
  * You misspelled a built-in dotnet command.
  * You intended to execute a .NET program, but dotnet---roll-forward does not exist.
  * You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.

[arturcic]

Can you run in a cmd this piece directly?
dotnet --roll-forward Major "C:\Users\chwille\.nuget\packages\gitversion.msbuild\6.0.0-beta.4\tools\/gitversion.dll" "C:\Workspace\src\myProject" -output file -outputfile obj\gitversion.json

[christophwille]

As I pointed out I did.

Edit: ah, there are subfolders in C:\Users\chwille.nuget\packages\gitversion.msbuild\6.0.0-beta.4\tools\ - if I add net8.0 eg to the path it works. So seems not to pick entire path.

[christophwille]

@arturcic is it possible to get a new beta package on nuget.org?

[arturcic]

@christophwille at this moment I cannot give an estimation when we get this released.

There is PR that needs to be reviewed, and as far as I understand there will be a couple more related to the trunk based implementation.

Let me check with @HHobeck if we can have a beta5 before he finishes his work.

[HHobeck]

Until now there is only one PR merged to master from me which includes only preparation changes for the actual refactoring task. It is up to you:

• review the changes and go forward
• create a package for one bugfix ;)

[arturcic]

@HHobeck, I think we can go with the beta5 and then your changes will get into beta6