-
Notifications
You must be signed in to change notification settings - Fork 235
Add correct dependency to get OS/process info in CoreCLR #278
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
Labels
Comments
daviwil
added a commit
that referenced
this issue
Aug 24, 2016
This change temporarily removes the OS and process information gathering from the CoreCLR version of PowerShell Editor Services because they cause assembly loading errors. This should be resolved by the upcoming conversion to the dotnet cli tools. Future resolution tracked by #278.
Interesting - this still a problem since we've switched to dotnot-cli tools? |
This required some dependency that I didn't have access to at the time. This is the place in the code where it was necessary: I think it should be fixable now but it isn't a super high priority. |
TylerLeonhardt
pushed a commit
to TylerLeonhardt/PowerShellEditorServices
that referenced
this issue
Feb 26, 2019
Update troubleshooting.md
This is done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To use the new
System.Runtime.InteropServices.RuntimeInformation
class to gather OS and process information for our initial logging in EditorServicesHost I'll need to pull in the expected dependency package since PowerShell doesn't seem to ship with it. This work won't be possible until we start the conversion over to the dotnet-cli tools.The text was updated successfully, but these errors were encountered: