deps.json for ProjectReferences is not emitted correctly
See original GitHub issueWhen I create a project with a project reference like this…
<ProjectReference Include="..\WindowsBase.csproj" />
… the deps.json
file that’s generated has an entry like this:
"WindowsBase/1.0.0": {
"runtime": {
"WindowsBase.dll": {}
}
}
The application loads WindowsBase
from Microsoft.NetCore.App
instead of loading the one supplied by the referenced project.
/cc @ericstj
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Visual Studio 2019 not adding referenced projects to deps. ...
The solution was to clear nuget's cache (for some reason)... Tools -> NuGet Package Manager -> Package Manager Console, type dotnet nuget ...
Read more >Project References - TypeScript: Documentation
Project references are a new feature in TypeScript 3.0 that allow you to structure your TypeScript programs into smaller pieces.
Read more >Fix unable to find *.deps.json for unit tests in .NET 5
Solution 1. Set ProduceReferenceAssembly to false · Solution 2. Ignore the /ref/ folder in your test tasks in Azure DevOps · Tobias Zimmergren....
Read more >TypeScript project references
json. TypeScript will generate a directed acyclic graph (DAG) and compile projects in order so that dependencies and references are resolved correctly.
Read more >Using TypeScript Project References with ts-loader and ...
json is correctly configured and TypeScript is able to resolve your modules, but webpack is not. Look into the resolve section of webpack.config ......
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
I bet you can workaround by using both a project reference and a raw file reference.
yeah having both kinds of references seems to be a useable workaround, loads the right System.Drawing now