GitVersion: StrictFilePathMarshaler must be used on a FilePath

One of our developers was consistently getting this error when building in Visual Studio 2015: Could not determine assembly version: StrictFilePathMarshaler must be used on a FilePath

I can see some references to this in libgit2sharp, and one in https://github.com/GitTools/GitVersion/pull/652.

The only remedy we could find under pressure was to re-clone the repository.

Unfortunately we needed to keep moving and don’t have the repository to reproduce it any more. Hopefully if anyone else gets this error message we can narrow down the root cause.

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Reactions: 2
  • Comments: 33 (25 by maintainers)

Most upvoted comments

@forestb, @roryprimrose: If what your experiences are infact the solution to this problem, that would be awesome. Ideas on how we can automate a check for different versions of GitVersion in the same solution?

@mkoertgen: I think I have identified the problem with the test in GitTools/GitTools.Core#38. As soon as that’s merged, released and upgraded in GitVersion, I hope we can get rid of this and the problem @cvpcs is having in #1070.

Today I ran into the same issue. Two instances of Visual Studio, each building unrelated sources from different git repos. Unfortunately at the same time on the same machine. On one side I have GitVersion-3.6.5, on the other GitVersion-4.0.0-beta12. As soon as I close one instance, the other works again; no matter in which order. This means, the v4-beta12 breaks when a v3.6.5 ran, and the other way round, too.