tag:help.appveyor.com,2012-11-13:/discussions/problems/24758-gitversion-5-not-working-on-visual-studio-2019-buildAppVeyor: Discussion 2020-04-03T18:47:20Ztag:help.appveyor.com,2012-11-13:Comment/475249672019-10-25T14:46:27Z2019-10-25T14:46:27ZGitVersion 5+ not working on Visual Studio 2019 build<div><p>Hit the same problem. Raised issue here:<br>
<a href="https://github.com/GitTools/GitVersion/issues/1869">https://github.com/GitTools/GitVersion/issues/1869</a></p></div>darrell.tunnelltag:help.appveyor.com,2012-11-13:Comment/475249672020-01-13T04:42:37Z2020-01-13T04:42:40ZGitVersion 5+ not working on Visual Studio 2019 build<div><p>Just to quickly follow up here: I've just commented on the issue linked by Darrell, as I ran into this today myself and was able to narrow it down to a particular release. I'll paste my comment content below. Hopefully this issue will eventually see some resolution, as I quite like GitVersion, and want to run the latest and greatest version thereof, but strongly prefer to keep it decoupled by using the portable version rather than the MSBuild tasks.</p>
<p>(comment text from here onward)</p>
<p>Upon encountering the same issue myself, I was able to narrow the failure to the following version: 4.0.1-beta.1+44.Branch.master.Sha.16c69e62d2a01696728411cb70cfa457551d8bd0</p>
<p>As the version immediately before it does not experience the problem: 4.0.1-beta.1+43.Branch.master.Sha.fc86cb2b6df90b300a5f4a50b1bd113b606c7c99</p>
<p>The changes in 4.0.1-beta.1+44, at least from the perspective of the source tree, seem innocuous. They appear unlikely to cause a problem unless an assembly binding redirect was deleted when it was in actuality required. Perhaps something downstream of the source tree? e.g. build and/or packaging for release?</p></div>Jeremy Graytag:help.appveyor.com,2012-11-13:Comment/475249672020-01-13T19:48:27Z2020-01-13T19:48:27ZGitVersion 5+ not working on Visual Studio 2019 build<div><p>Hi Jeremy,</p>
<p>GitVersion 5.1.3 was in VS 2019 image update 4 days ago: <a href="https://www.appveyor.com/updates/2020/01/09/">https://www.appveyor.com/updates/2020/01/09/</a></p>
<p>Did you have a chance to give it a try? Does it still have the issue on our environment?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/475249672020-01-13T21:39:14Z2020-01-13T21:39:16ZGitVersion 5+ not working on Visual Studio 2019 build<div><p>Hey there Feodor. As things turn out, if I remove the use of Chocolatey and simply use the version in the image then everything works. I imagine there's something up with the Chocolatey version and, if nothing else, GitVersion's appveyor.yml generation (as unless I'm mistaken I recall it being the thing that set up the choco install in the first place.)</p></div>Jeremy Graytag:help.appveyor.com,2012-11-13:Comment/475249672020-01-13T21:48:02Z2020-01-13T21:48:02ZGitVersion 5+ not working on Visual Studio 2019 build<div><p>OK, that's interesting. If you look at <code>chocolateyInstall.ps1</code> for GitVersion <a href="https://chocolatey.org/packages/GitVersion.Portable/5.1.3#files">https://chocolatey.org/packages/GitVersion.Portable/5.1.3#files</a> you'll see there <code>Generate-BinFile ...</code> - my guess is that it's Chocolatey's shim being generated and this could be something related to that. On AppVeyor environment GitVersion is installed from NuGet package and GitVersion.exe is called directly.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/475249672020-01-19T22:26:08Z2020-01-19T22:26:08ZGitVersion 5+ not working on Visual Studio 2019 build<div><p>The updated VM worked for me and has solved the issue. Thanks for letting me know about the update.</p></div>bentag:help.appveyor.com,2012-11-13:Comment/475249672020-01-19T23:38:56Z2020-01-19T23:38:56ZGitVersion 5+ not working on Visual Studio 2019 build<div><p>Thanks for the update!</p></div>Feodor Fitsner