Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix automapper dependency #106

Merged
merged 1 commit into from
Jul 10, 2023
Merged

Fix automapper dependency #106

merged 1 commit into from
Jul 10, 2023

Conversation

kzu
Copy link
Member

@kzu kzu commented Jul 10, 2023

If we don't specify the target framework, the packaging project will just take a dependency with no framework. This doesn't work when we also have framework-specific dependencies, and will cause the dependency to be lost entirely when nuget performs a restore.

In other words, if you have non-framework specific dependencies AND framework specific dependencies, you will only get the latter in the restore graph.

If we don't specify the target framework, the packaging project will just take a dependency with no framework. This doesn't work when we *also* have framework-specific dependencies, and will cause the dependency to be lost entirely when nuget performs a restore.

In other words, if you have non-framework specific dependencies AND framework specific dependencies, you will only get the latter in the restore graph.
@kzu kzu added the bug Something isn't working label Jul 10, 2023
@kzu kzu enabled auto-merge (rebase) July 10, 2023 22:17
@kzu kzu merged commit 349ea80 into main Jul 10, 2023
7 checks passed
@kzu kzu deleted the dev/automapper branch July 10, 2023 22:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant