Skip to content

Remove Nito.AsyncEx dependency, add replacements #116

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

Merged
merged 1 commit into from
Jan 25, 2016

Conversation

daviwil
Copy link
Contributor

@daviwil daviwil commented Jan 25, 2016

This change removes all uses of the Nito.AsyncEx NuGet package from the
solution. This change was made to remove the use of this third-party
dependency so that consumers don't need to get extra open-source approval
when using PowerShell Editor Services.

Removing this dependency required the creation of our own custom
implementations of the classes we were using from Nito.AsyncEx. These new
classes were written from scratch.

Resolves #115

This change removes all uses of the Nito.AsyncEx NuGet package from the
solution.  This change was made to remove the use of this third-party
dependency so that consumers don't need to get extra open-source approval
when using PowerShell Editor Services.

Removing this dependency required the creation of our own custom
implementations of the classes we were using from Nito.AsyncEx.  These new
classes were written from scratch.

Resolves #115
@daviwil daviwil force-pushed the daviwil/remove-asyncex branch from 154f7e6 to 0fe1a84 Compare January 25, 2016 01:53
daviwil added a commit that referenced this pull request Jan 25, 2016
Remove Nito.AsyncEx dependency, add replacements
@daviwil daviwil merged commit 8636d56 into master Jan 25, 2016
@daviwil daviwil deleted the daviwil/remove-asyncex branch January 25, 2016 02:52
TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this pull request Feb 26, 2019
…itignore-again

Adding foo[1].txt to .gitignore for when I'm building in the vscode-p…
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.

2 participants