Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cannot transitively reference a csproj+project.json
See original GitHub issueSteps to reproduce
- Clone https://github.com/gulbanana/repro-transitive-projectjson
dotnet build- error MSB4025: The project file could not be loaded. Data at the root level is invalid. Line 1, position 1.
The bug also occurs when building in Visual Studio.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
New .csproj cannot reference a traditional .csproj #1730
I found a workaround: every new .csproj project must directly reference every transitively-referenced project.json project to avoid this bug ...
Read more >c# - Disable transitive project reference in .NET Standard 2
csproj that references projects for which you don't want their transitive dependencies to be visible by compiler.
Read more >PackageReference in project files - NuGet
This will enable packages that those projects refer to, to be "transitively" referenced by your project.
Read more >Managing Dependencies in .NET: .csproj, .packages.config ...
A project was represented by a .csproj file but the dependencies (including NuGet package references) were kept separately in a ...
Read more >Old csproj to new csproj: Visual Studio 2017 upgrade guide
NET Core went from the project.json to csproj file format, and the new ... Also, MSBuild now does transitive project-to-project references ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That workaround works (around) for me.
Let’s track it though #922.