-
Notifications
You must be signed in to change notification settings - Fork 252
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
Target Segment in . targets file in buildTransitive not work #12223
Comments
output like this 已启动重新生成… |
Hello, MSBuild also made some changes recently. The default was changed with VS 2022 (17.0) (dotnet/msbuild#6622). It looks you're using VS 2019, so the default is still set to
Please take a look and let us know if you're able to resolve your issue. |
but my vs2022 has the same action ; |
When I change Porject A and Project B to sdk-style project it works |
@Y-Theta Please see https://learn.microsoft.com/nuget/consume-packages/package-references-in-project-files#using-packagereference-for-a-project-with-no-package-dependencies SDK styles default to PackageReference, as they don't support packages.config. But as the docs say, for non-SDK style projects, a project either needs a PackageReference, or to define the RestoreProjectStyle. |
This issue has been automatically marked as stale because we have not received a response in 14 days. It will be closed if no further activity occurs within another 14 days of this comment. |
NuGet Product Used
NuGet.exe
Product Version
nuget.exe 6.3.0.131
Worked before?
No response
Impact
It's more difficult to complete my work
Repro Steps & Context
create a package with struct like
mctech.lib.desktopcapture
-1.4.2
-buildTransitive
-net47
-McTech.Lib.DesktopCapture.targets
and in the targets
have a
create a classlibrary project using netframework 4.7 named A
create a winform project using netframework 4.7 named B
in Project B make a project reference to A
in Project A make a PackageReference to the package
when rebuild Project B
only project A output has the message
Verbose Logs
No response
The text was updated successfully, but these errors were encountered: