Build extension using VSMac SDK #50
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Instead of depending on being built as part of the vsmac solution.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is not ready yet. 😸
Initial work allowing an mpack to be built out of this repo instead of VSMac submoduling to build it.
The biggest outstanding question is what to do with
Microsoft.CodeAnalysis.ExternalAccess.FSharp.dll. VSMac end up bundling it with this extension, so it's a little weird to build+ship it in VSMac and have this extension reference it from the VSMac app bundle. I'd like to better understand why we forked, what would be involved in unforking, and if it would make more sense to move that code into this repo (along with the fsi service and tests).Once that flow is figured out, I will set up CI.