-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
error NETSDK1005: Assets file 'D:\a\1\s\...\project.assets.json' doesn't have a target for '.NETStandard,Version=v1.5' #2720
Comments
Please note that all the project.assets.json files and the verbose msbuild log are all available from the Azure Pipeline build I link to above as build artifacts. |
I think this may be a regression in 15.9.x, since commits we were able to build a couple months ago can no longer be built. |
Looking at binlog, there is something wrong in TFM negotiation between P2P here. Microsoft.VisualStudio.Composition is building Microsoft.VisualStudio.LocalizationShell with TargetFramework=netstandard1.5 global property, which is not a valid TFM for the latter. There's a solution build dependency that triggers this. This looks like another bug I investigated a little while ago, but I do not recall the msbuild versions impacted. I will search for it. |
Looks exactly like dotnet/msbuild#3626, but that was supposed to be fixed in 15.9, not caused by 15.9. |
Binlog has this:
@AArnott Is it possible you downgraded to 15.8 RTM from 15.9 preview in pipelines rather than upgraded to 15.9 RTM? |
Could also have happened if pipelines was previously on 15.7 and now moved to 15.8. That's where the actual regression happened, and it was fixed in 15.9. Actually upgrading to 15.9 should resolve this. |
Thanks, @nguerrera. Unfortunately I can't influence when these cloud build hosts upgrade to 15.9. But since you mentioned solution dependencies are involved (which I rarely use, but do in this solution), I tried simply removing the solution dep, which I can't remember why I even needed. I'll see if I can get that route to work. :) |
Duplicate of dotnet/msbuild#3626 |
Ya, removing the solution dependency (and using ProjectReference with a |
…907.1 (#2720) - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19457.1
Very similar to #1321, except that it works fine on my own machine, but consistently fails when run in Azure Pipelines.
The LocalizationShell project targets netstandard1.0, and is referenced by a multitargeting project that targets several frameworks including netstandard1.5.
The odd thing is this works on my machine, on AppVeyor, and even on Azure Pipelines in the past. But now it's consistently failing.
This may be a dupe of #2563
The text was updated successfully, but these errors were encountered: