libgit2 / libgit2/libgit2sharp
Can't parse project with reference to libgit2sharp
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
Reproduction steps
- Reference libgit2sharp in the project
- Call
new Microsoft.Build.Evaluation.Project.Project("path/to/.csproj")
Expected behavior
Project parsed successfully
Actual behavior
Microsoft.Build.Exceptions.InvalidProjectFileException: 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. c:\root\packages\LibGit2Sharp.NativeBinaries.1.0.217\build\net461\LibGit2Sharp.NativeBinaries.props
Version of LibGit2Sharp (release number or SHA1)
0.25.2
Operating system(s) tested; .NET runtime tested
Windows Server 2016
.NET 4.6.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Microsoft.Build.Evaluation.Project.Project call on Windows Server 2016 with .NET 4.6.1, then inspect LibGit2Sharp.NativeBinaries.1.0.217/build/net461/LibGit2Sharp.NativeBinaries.props. Done means the project parses successfully when LibGit2Sharp is referenced, without the InvalidProjectFileException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100