You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
build on local machine success but when build with TFS error
.NET Framework 4.6.1
packages\DlibDotNet.19.21.0.20210302\build\DlibDotNet.props(2,1): Error MSB4041: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.
The text was updated successfully, but these errors were encountered:
check *.nuspec files, for the line <file src="build\DlibDotNet.Native.props" target="build\DlibDotNet.props" />
@gholami3000
This issue is about making changes to the DlibDotNet.Native.props format to be compatible with fallback to older build tools.
Start from checking if TFS has proper version of BuildTools for x86 platform, v15 or v16, and install accordingly to fix this issue.
Replacing <Project version="4.0"> line with the following <Project version="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> should fix the issue, and make package compatible with older build tools.
@takuya-takeuchi if trying to declaring minimum build tools needed, it could broke existing projects I suppose,
that needed to be investigated further.
build on local machine success but when build with TFS error
.NET Framework 4.6.1
packages\DlibDotNet.19.21.0.20210302\build\DlibDotNet.props(2,1): Error MSB4041: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.
The text was updated successfully, but these errors were encountered: