Test the EditorFeatures layer on net472 and net6.0-windows#61234
Test the EditorFeatures layer on net472 and net6.0-windows#61234sharwell wants to merge 10 commits intodotnet:mainfrom
Conversation
…et net6.0-windows Also update Microsoft.CodeAnalysis.CSharp.EditorFeatures2.UnitTests, which was split from the above.
src/Workspaces/Core/Portable/Microsoft.CodeAnalysis.Workspaces.csproj
Outdated
Show resolved
Hide resolved
| => GetTestProject(documentId.ProjectId); | ||
|
|
||
| public TestHostProject GetTestProject(ProjectId projectId) | ||
| public TestHostProject? GetTestProject(ProjectId projectId) |
There was a problem hiding this comment.
Do we want to add GetRequired versions of these?
|
@sharwell Could we revive this PR? Now our OOP is running on .NET 6, there's a big gap in our test coverage. |
|
I see the following errors in the correctness build log, but not in other legs. I'm curious why is that (I don't really know what correctness legs are for)? @jaredpar |
This particular check is to ensure we don't accidentally add new TFM into our builds. It's less of a problem now but a few years ago we had a real problem with random TFM getting added into our builds that should never have been a part of the product. It took some time to unwind that. Now we have a check that ensures we are notified when new TFM are added to the build. This is similar to how we have public API files. It's not wrong to add a new public API but we want to make sure it's a very visible process. Simply add the TFM here
These are jobs that ensure our repository is building correctly and in the manner we expect. Think of it as unit test for how we build. This covers everything from build style up to actual build correctness (ensure no double writes, bootstrap hosting, anaylzers, etc ...) |
|
Moving to draft as this pull request hasn't gone anywhere. |
Issues for disabled code and tests:
#ron .NET 6.0 #61233