Skip to content

Upgrading V9 to V10 causes dependency missing errors #4324

@BlythMeister

Description

@BlythMeister

It would appear this is related to changes in the paket.targets.

The error we get on build is that there are missing dependencies.

These are framework projects targetting 4.7.1.

A big difference i can see in the generated "obj" files is that in project.assets.json all dependencies are now missing.
The same is trie in the csproj.nuget.dgspec.json under the "net471" framework.

I think it's this change #4247

The dependencies file we have:

source https://[REDACTED]
source https://[REDACTED]
source https://[REDACTED]
strategy: min
redirects: on

nuget package1
nuget package2 ~> 1.0.0

the lock file adds restriction: >= net471 to all top level dependency lines.

the reference file has all the dependencies we reference, 99.9% of which will be 2nd level dependencies (so in the lock, but not in the dependencies file)

we use "package2" to set a standardised version of all external dependencies across multiple repository

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions