dotnet restore should skip unsupported projects
See original GitHub issueCopied from here: https://github.com/Microsoft/nodejstools/issues/1492#issuecomment-373016358
dotnet restore
/opt/atlassian/pipelines/agent/build/src/Company.Project.Client/Company.Project.Client.njsproj
(81,3): error MSB4019: The imported project "/usr/share/dotnet/sdk/2.1.101/Microsoft/VisualStudio/v15.0/Node.js Tools/Microsoft.NodejsTools.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
But instead of crashing shouldn’t it just ignore .nsproj files then? I’m justing running dotnet restore in the root of my folder. And it will not finish because there are .nsproj files there.
Thoughts, or is @starquake missing an option?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6 (4 by maintainers)
Top Results From Across the Web
net - dotnet restore: exclude project
1. Have you tried to skip this project from build in solution properties? – Pavel Anikhouski. Dec 2, 2019 at 11:55 · Right...
Read more >dotnet restore command - .NET CLI
Learn how to restore dependencies and project-specific tools with the dotnet restore command.
Read more >Troubleshooting NuGet Package Restore in Visual Studio
If you're using Visual Studio, first enable package restore as follows. Otherwise continue to the sections that follow.
Read more >NuGet Warning NU1503
Skipping restore for project 'c:\a.csproj'. The project file may be invalid or missing targets required for restore.
Read more >Publish ReadyToRun with --no-restore requires changes
Learn about the breaking change in .NET 6 where publishing a project with ReadyToRun requires changes to the way the project is restored....
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 FreeTop 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
Top GitHub Comments
We can’t ignore projects we don’t know because we don’t know which projects we actually don’t know about. For instance, natively, the CLI does not support UAP projects, however, with the addition of a PackageReference, everything works.
We don’t whitelist supported projects because there is no way for that list to be authoritative.
@mdg1019 There is an issue filed on NuGet for this already and I have pointed to it in my comment above.