(MODULES-6930) Fix Pipes Server On windows2008r2 #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The newest image for Windows 2008r2 is exhibiting different behavior for loading .NET assemblies than we have seen in the past. The System.Core assembly is not loaded into the PowerShell host process by default any longer. This causes the init.ps1 script in the module to to fail to start a Pipe Server to receive PowerShell scripts to be executed. This change always attempts to load the System.Core assembly prior to creating the pipe server object. Explicity loading the assembly fixes the issue and the newest image becomes usable again.
jpogran
approved these changes
Apr 5, 2018
RandomNoun7
deleted the
tickets/master/MODULES-6930-fix-pipes-server-in-windows2008r2
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The newest image for Windows 2008r2 is exhibiting different behavior
for loading .NET assemblies than we have seen in the past. The
System.Core assembly is not loaded into the PowerShell host process by
default any longer. This causes the init.ps1 script in the module to
to fail to start a Pipe Server to receive PowerShell scripts to be
executed. This change always attempts to load the System.Core
assembly prior to creating the pipe server object. Explicity loading the
assembly fixes the issue and the newest image becomes usable again.