Skip to content

Fix crash in ScriptRule parsing when PowerShell help system is not initialized on a machine #166

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 2 commits into from
May 15, 2015

Conversation

raghushantha
Copy link
Member

Verified the fix in elevated/non-elevated environment with/without help system initialization

@yutingc
Copy link
Contributor

yutingc commented May 15, 2015

Changes look good. One question I have is that will adding update-help impact the perfomance? Will it hang a few seconds?

@raghushantha
Copy link
Member Author

The perf impact is negligible because of:
I am looking for help for a specific module - so not all help is downloaded
the help does not exist out the box for this module - so no help files are downloaded

Verified this on a clean-install machine.

@raghushantha
Copy link
Member Author

Also, the build is failing since appveyor changes are not integrated with BugFixes

raghushantha added a commit that referenced this pull request May 15, 2015
Fix crash in ScriptRule parsing when PowerShell help system is not initialized on a machine
@raghushantha raghushantha merged commit 616e570 into BugFixes May 15, 2015
@yutingc
Copy link
Contributor

yutingc commented May 15, 2015

But do we need to call update-help each time when we import customized rule? Is there a way to only download help when there was no "get-help"?

@raghushantha
Copy link
Member Author

Update-Help optimizes this. it sets up a registry key after the first time.

@raghushantha raghushantha deleted the ScriptRuleCrashFixBranch branch May 15, 2015 20:59
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