locked
the default xml namespace of the project must be msbuild 2003 RRS feed

  • Question

  • User2012297617 posted

    I'm using Visual Studio 2017. I created a build definition to automate our build process.

    For some reason, I'm getting this error: the default xml namespace of the project must be msbuild 2003. If the project is authored in the MSBuild 2003 format, please add xmlmsn = http://schema.microsoft.com/developer/msbuild/2003 to the <Project>.

    Has anybody experience this error?  Is this an issue in .NET Core?

    Wednesday, January 8, 2020 9:07 PM

Answers

  • User1535942433 posted

    Hi lesponce,

    As far as I think,this is an issue in .NET Core.Starting from VisualStudio 2015 MSBuild is provided as part of IDE (or build tools).

    I suggest you could creat a MSbuild project,build properties and items.

    Note:You must specify the xmlns namespace in the Project element. If ToolsVersion is present in a new project, it must be "15.0".

    More details, you could refer to below article:

    https://docs.microsoft.com/en-us/visualstudio/msbuild/walkthrough-using-msbuild?view=vs-2017

    Best regards,

    Yijing Sun

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, January 9, 2020 2:06 AM

All replies

  • User1535942433 posted

    Hi lesponce,

    As far as I think,this is an issue in .NET Core.Starting from VisualStudio 2015 MSBuild is provided as part of IDE (or build tools).

    I suggest you could creat a MSbuild project,build properties and items.

    Note:You must specify the xmlns namespace in the Project element. If ToolsVersion is present in a new project, it must be "15.0".

    More details, you could refer to below article:

    https://docs.microsoft.com/en-us/visualstudio/msbuild/walkthrough-using-msbuild?view=vs-2017

    Best regards,

    Yijing Sun

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, January 9, 2020 2:06 AM
  • User2012297617 posted

    Yes, it seems like the issue is related to .NET Core.  I might go a different route.  Thanks for your feedback.

    Thursday, January 9, 2020 8:50 PM