Skip to content
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

Migrate to new SDK. #94

Merged
merged 1 commit into from
Feb 19, 2020
Merged

Migrate to new SDK. #94

merged 1 commit into from
Feb 19, 2020

Conversation

mfilippov
Copy link
Collaborator

No description provided.

@nojaf
Copy link
Contributor

nojaf commented Feb 19, 2020

Out of curiosity, is this the .NET Core SDK?

@auduchinok
Copy link
Member

auduchinok commented Feb 19, 2020

@nojaf It's a temporary name for a unified R#/Rider SDK which is needed for our internal CI.

@NinoFloris
Copy link

How would we be able to run this?

@auduchinok
Copy link
Member

@NinoFloris Building and running the plugin should work exactly the same way as it is now, and we're evaluating that the change doesn't break anything for non-CI scenarios.

@nojaf
Copy link
Contributor

nojaf commented Feb 19, 2020

@auduchinok I saw a tweet from @kskrygan mentioning that that Rider backend services would run completely on .NET Core in 2020.1 and I was wondering if this SDK was the one he mentioned.

@auduchinok
Copy link
Member

@nojaf Ah, I see. No, it's not related to the runtime migration, just changes of how our SDK is constructed and referenced in the bundled plugins.

@auduchinok auduchinok merged commit d8351e8 into net201 Feb 19, 2020
@auduchinok auduchinok deleted the net201-mf-new-sdk branch February 20, 2020 13:42
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.

4 participants