Skip to content

Fixes issue with notepad.exe running correctly. #144

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

Conversation

rkeithhill
Copy link
Contributor

For some reason, the PowerShell engine thinks notepad.exe is a command-line app and calls the SessionPSHost BeginNotifyApplication() which used to throw NotImplementedException. It now just logs the call.

Also updated the PSHost version to pull the version from the services dll. I tried several ways to pull from the host app (reflection Process.GetCurrentProcess().MainModule) but both caused the unit tests to hang.

For some reason, the PowerShell engine thinks notepad.exe is a command-line app and calls the SessionPSHost BeginNotifyApplication() which used to throw NotImplementedException.  It now just logs the call.  Also updated the PSHost version to pull the version from the services dll.  I tried several ways to pull from the host app (reflection Process.GetCurrentProcess().MainModule) but both caused the unit tests to hang.
@daviwil
Copy link
Contributor

daviwil commented Feb 8, 2016

Great! Thanks for doing this.

daviwil added a commit that referenced this pull request Feb 8, 2016
…lure

Fixes issue with notepad.exe running correctly.
@daviwil daviwil merged commit 38256ae into PowerShell:master Feb 8, 2016
@rkeithhill rkeithhill deleted the rkeithhill/notepad-launch-failure branch February 8, 2016 00:21
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