Skip to content

Conversation

@ryanbrandenburg
Copy link
Contributor

@ryanbrandenburg ryanbrandenburg commented Dec 22, 2022

Summary of the changes

  • We're turning this dll into a true ExternalAccess dll.

Fixes: Part of #6945.

@ryanbrandenburg ryanbrandenburg requested review from a team as code owners December 22, 2022 22:40
Copy link
Member

@davidwengier davidwengier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I no understand

@ryanbrandenburg
Copy link
Contributor Author

No merging this until at least Friday.

@davidwengier
Copy link
Member

Can you update the description with what this is intended to do and how it helps? I've forgotten most of the context here.

Also, do we need to coordinate anything with O# given the rename of a DLL? Or do/did they just use the non-strong-named one?

@davidwengier
Copy link
Member

No merging this until at least Friday.

We should probably wait for Allison's branch to merge in, too

Copy link
Member

@davidwengier davidwengier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a nice and small EA project :)

Should add the public API analyzers before merging (unless you're going back to IVTs in the end?)

Copy link
Contributor

@allisonchou allisonchou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Per our earlier convo I don't think this should break anything, crossing fingers

[InlineData(nameof(OmniSharpProjectChangeKind.DocumentAdded))]
[InlineData(nameof(OmniSharpProjectChangeKind.DocumentRemoved))]
[InlineData(nameof(OmniSharpProjectChangeKind.ProjectChanged))]
public async Task ProjectManager_Changed_EnqueuesPublish(string changeKindStr)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the VS Code tests were actually disabled in CI a while ago, lol might be good to eventually verify they still work/pass 😅 (prob can be done in a different PR)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants