-
Notifications
You must be signed in to change notification settings - Fork 4k
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
EditorFeatures.Cocoa: Build with net6.0 #59429
Conversation
@KirillOsenkov @Therzok @davidwengier @tmat jfyi. I'm not sure exactly when this will be ready for review. We'll likely need it for your 17.2. |
|
8e417c7
to
e3cbe65
Compare
I wonder what this is about. Anyway, I'll need to fix that P14 of the macos workload is being used instead of P13. |
d44a16a
to
c9bd537
Compare
I used a backport of this PR to bring this into VSMac. To finish this PR, I need to get a few editor packages published. Should be able to get that done next week after some signing infrastructure issues are addressed. |
30fa881
to
f40f22c
Compare
3c6cceb
to
9cf9d71
Compare
2f93672
to
a28402a
Compare
I had previously done work inside In the long run, workload management may move to be a common Arcade feature. |
src/EditorFeatures/Core.Cocoa/Microsoft.CodeAnalysis.EditorFeatures.Cocoa.csproj
Outdated
Show resolved
Hide resolved
src/EditorFeatures/Core.Cocoa/Microsoft.CodeAnalysis.EditorFeatures.Cocoa.csproj
Outdated
Show resolved
Hide resolved
Also switch ps1 to 2 space indenting.
In CI, we keep seeing errors like: ``` Workload installation failed: Failed to validate package signing. Verifying Microsoft.NET.Runtime.MonoAOTCompiler.Task.6.0.2-mauipre.1.22102.15 error: NU3004: The package is not signed. Package signature validation failed. ``` This is presumably happening because NuGet.config references multiple feeds, some of which have signed versions of workload packages, and some of which have unsigned versions. We can untangle this later. For now, change EditorFeatures.Cocoa to target `net6.0` instead of `net6.0-macos`, and manually reference the assemblies it needs from the macos SDK and the VS editor.
a5219ac
to
fcf1314
Compare
/azp run |
Azure Pipelines successfully started running 4 pipeline(s). |
When I rebased yesterday I think there was only one failure. After your |
Odd. When I did the azp run I'm 90% sure all of the various integration tests were failing. If it was just one, I normally just re-run that one Generally speaking, yes we're in a bit of a "re-run until they turn green" situation, though with new editor APIs it is worth at least checking if the failures are consistent, and investigating. Looks like the |
The stack in the Go To Base test failure seems to imply an issue with the shell:
It runs fine and passes on my machine, but that probably doesn't mean much. @sharwell any ideas? Is this the first test run with the new |
Okay, everything is green.. stand back, I'm gonna merge it! |
Thanks David! |
What version of VS is needed to work with these changes? Trying to figure out the expected lifetime of the -vs-deps branch here. |
you mean VSWin or VSMac? |
Just VSWin, I think. Once a public preview comes out which can F5 successfully on whatever we have in main-vs-deps, we'd like to shut down the -vs-deps branch and go back to just shipping out of main. |
Use macos workload
12.1.200-preview.13.7
. Necessitates bumping the editor and several other packages to 17.2 (17.1.387 might also be OK for editor).Adapt workload installation script for bash (unless we can use pwsh in unix pipelines?)