[MSBuild]::NormalizeDirectory, Not Found

[wahmedswl]

Hi,
Recent build of GitInfo is broken, getting error

"C:\gitlab\builds\70fbc2c0\0\SequelMed\SequelMedServerSide\SequelMed\SequelMed.vbproj" (Build target) (1) ->
(_GitRoot target) -> 
  C:\gitlab\builds\70fbc2c0\0\SequelMed\SequelMedServerSide\packages\GitInfo\build\GitInfo.targets(185,4): error MSB4186: Invalid static method invocation syntax: "[MSBuild]::NormalizeDirectory($(_GitOutput.Trim()))". Method '[MSBuild]::NormalizeDirectory' not found. Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(`a`, `b`)).  [C:\gitlab\builds\70fbc2c0\0\SequelMed\SequelMedServerSide\SequelMed\SequelMed.vbproj]

    0 Warning(s)
    1 Error(s)

MSBuild: C:\Program Files (x86)\MSBuild\14.0

[kzu]

Ugh, @alanmcgovern?

On Fri, Aug 3, 2018, 7:06 AM Waqas Ahmed ***@***.***> wrote: Hi, Recent build of GitInfo is broken, getting error "C:\gitlab\builds\70fbc2c0\0\SequelMed\SequelMedServerSide\SequelMed\SequelMed.vbproj" (Build target) (1) -> (_GitRoot target) -> C:\gitlab\builds\70fbc2c0\0\SequelMed\SequelMedServerSide\packages\GitInfo\build\GitInfo.targets(185,4): error MSB4186: Invalid static method invocation syntax: "[MSBuild]::NormalizeDirectory($(_GitOutput.Trim()))". Method '[MSBuild]::NormalizeDirectory' not found. Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(`a`, `b`)). [C:\gitlab\builds\70fbc2c0\0\SequelMed\SequelMedServerSide\SequelMed\SequelMed.vbproj] 0 Warning(s) 1 Error(s) MSBuild: C:\Program Files (x86)\MSBuild\14.0 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#74>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKW6623a9VmCWhTdQ3McKN31-wg-6ovks5uNCCsgaJpZM4VtuNN> .

--

…

-- /kzu from mobile

[kzu]

Fixed in 3228678

[wahmedswl]

Hi, when next version will be available? GitInfo ci builds also got failed.

[kzu]

It's up now

[wahmedswl]

Hi, we are again getting this error

C:\gitlab\builds\70fbc2c0\0\PracticeEHR\AdminSupportPortal\AdminSupportPortal\AdminSupportPortal.csproj" (Build target) (1) ->
(_GitRoot target) -> 
  C:\gitlab\builds\70fbc2c0\0\PracticeEHR\AdminSupportPortal\packages\GitInfo\build\GitInfo.targets(185,4): error MSB4186: Invalid static method invocation syntax: "[MSBuild]::NormalizeDirectory($(_GitOutput.Trim()))". Method '[MSBuild]::NormalizeDirectory' not found. Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(`a`, `b`)).  [C:\gitlab\builds\70fbc2c0\0\PracticeEHR\AdminSupportPortal\AdminSupportPortal\AdminSupportPortal.csproj]

GitInfo 2.0.15

is there anything related to VS version? Thanks

[kzu]

What's your build environment?--

…

-- /kzu from mobile

[wahmedswl]

Hi, we are using VS2015.

Thanks

[kzu]

I'll need a binlog (see http://msbuildlog.com) to diagnose properly.

Thanks!

[nexusw]

Same here:
Ungültige Aufrufsyntax für statische Methode: "[MSBuild]::NormalizeDirectory($(_GitOutput.Trim()))". Die Methode "[MSBuild]::NormalizeDirectory" konnte nicht gefunden werden. Für den Aufruf statischer Methoden muss folgendes Format verwendet werden: $([vollständiger Typname]::Methode()), z. B. $([System.IO.Path]::Combine(a, b))

used NuGet version of GitInfo: 2.0.20
and
Microsoft Visual Studio Professional 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Version 4.7.03056

[kzu]

OS and MSBuild version?

On Tue, Jan 8, 2019, 10:17 AM nexusw ***@***.***> wrote: Same here: Ungültige Aufrufsyntax für statische Methode: "[MSBuild]::NormalizeDirectory($(_GitOutput.Trim()))". Die Methode "[MSBuild]::NormalizeDirectory" konnte nicht gefunden werden. Für den Aufruf statischer Methoden muss folgendes Format verwendet werden: $([vollständiger Typname]::Methode()), z. B. $([System.IO.Path]::Combine(a, b)) used NuGet version of GitInfo: 2.0.20 — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#74 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKW6xAcfvAYV6ps_CoSSrhXzCs92LBkks5vBJpPgaJpZM4VtuNN> .

--

…

-- @kzu from mobile

[nexusw]

OS: Win 10 Pro with Version 1803
Visual Studio Pro 2015 uses MSBuild 14.0
(project is compiled for .Net Framework 4.5.2 (with c#6 as language version)

I found out that NormalizeDirectory() is new to MSBuild v15?:
https://docs.microsoft.com/de-de/visualstudio/msbuild/what-s-new-in-msbuild-15-0?view=vs-2017

I try to install MSBuild v15 as described in:
https://stackoverflow.com/questions/42696948/how-can-i-install-the-vs2017-version-of-msbuild-on-a-build-server-without-instal

But how can i tell Visual studio which MSBuild to use?
I didn't find a working way to do so. Setting ToolsVersion="15.0" in .csproj or your GitInfo.target files are ignored. Informations found at:
https://stackoverflow.com/questions/34065614/is-there-a-simple-way-to-make-visual-studio-2015-use-a-specific-toolsversion
https://stackoverflow.com/questions/42103232/vs2015-how-to-build-using-msbuild-12-0

As a workaround i removed:
NormalizeDirectory(..)
and use only:
<GitRoot>$(_GitOutput.Trim())</GitRoot>
in GitInfo.targets (lines 185 and 201)

This way compilation is done without errors and e.g. ThisAssembly.Git.Tag works fine.

[wahmedswl]

@kzu plz re-open this ticket also as its not still fixed.

Thanks

[kzu]

@alanmcgovern so if we replace all instances of NormalizeDirectory with NromalizePath and add a TrimEnd('/', '\') it should work, right?

[nexusw]

Im not sure about that, because i also tried NormalizePath() with no luck. It is also listed in the new features of MsBuild v15.0.
I will doublecheck tomorrow.

[okhiyaev]

This issue is related to VS2015, when i used VS2019 the issue no longer occured.
Using GitIfno 2.0.20

[kzu]

Yeah, it looks it's MSBuild 15+ only function. We'd need to condition all the places we use Normalize and do something different :(.

[kzu]

By now, MSBuild 15+ is everywhere. No point in fixing it (and nobody volunteered either, so I guess it wasn't too critical either :)).