-
Notifications
You must be signed in to change notification settings - Fork 516
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
[net7.0-rc2] Creating a cross-targeted library with net6.0-mac fails with an obscure error #16400
Comments
Can you get a binlog from a command line build?
That will tell us exactly what you have installed and what's loaded during the build. |
Hi @jeromelaban. We have added the "need-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
I wish I had taken the binlog before creating the issue and fixing it :) I'll see if I can remove the workload to repro. |
Here's some update. The above message only happens when built from VS windows, not on the CLI. Here's the binlog captured from VS: issue16400.zip and the CLI: 16400-msbuild-cli.zip |
…t exists. Fixes xamarin#16400. Hopefully fixes xamarin#16400.
Looks like this happens when the IDE executes the |
Tentative fix: rolfbjarne@af47d23 (for .NET 8). |
This happens with most of the visual studio templates. About the only thing that works is the WSP. The other stuff is just vaporware. For example on a fresh project with a fresh install of the latest Visual Studio 2022, when you build the multi platform solution you get: Failed to restore C:\Users\steve\source\repos\NotitraceClient\NotitraceClient.csproj (in 3 ms). |
I am hitting this error message, even though the macos workload is installed:
Build error:
I am trying to create a new cross-platform UNO library, but hitting this bug. Any ideas? How can I work around this? |
@lukasf this generally happens because VS does not install the macos workload by default (among some other unknown parts). You can try going into the |
Thank you. This solved my problem. It is a bit weird though, that I have to install the macos workload when it is already shown in the list of installed workloads. When running the command, I even got a warning that it is already installed, but then it started installing a whole lot of stuff and now it builds correctly. |
…t exists. Fixes xamarin#16400. Hopefully fixes xamarin#16400.
…t exists. Fixes xamarin#16400. Hopefully fixes xamarin#16400.
…arget.targets file if it exists. Fixes #16400. (#17516) Hopefully fixes #16400. Backport of #17498 Co-authored-by: Rolf Bjarne Kvinge <[email protected]>
Steps to Reproduce
Without having the macos SDK installed, build the following:
Expected Behavior
An error from .NET SDK to flag that a workload is missing.
Actual Behavior
Environment
Build Logs
The text was updated successfully, but these errors were encountered: