Skip to content

Set-Content on Unix system not working with created PSDrives with the FileSystem provider - #2430

Closed
James Truher (JamesWTruher) wants to merge 1 commit into
PowerShell:masterfrom
JamesWTruher:jameswtruher/SetContentWithDrive
Closed

James Truher (JamesWTruher) wants to merge 1 commit into
PowerShell:masterfrom
JamesWTruher:jameswtruher/SetContentWithDrive

Conversation

@JamesWTruher

Copy link
Copy Markdown
Collaborator

Also activate the tests which were marked as skipped for those tests

Anything that went against the single rooted drive was fine, but

new-psdrive -name TEMP -root /tmp -psprovider filesystem`
set-content TEMP:/file

would fail

Also activate the tests which were marked as skipped for those tests
@msftclas

Hi James Truher (@JamesWTruher), I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!


It looks like you're a Microsoft contributor (Jim Truher). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@JamesWTruher

James Truher (JamesWTruher) commented Oct 6, 2016 •

Copy link
Copy Markdown
Collaborator Author

PR #2392 is a better change (this one is too specific to set-content) - Charu will take these tests

@JamesWTruher
James Truher (JamesWTruher) deleted the jameswtruher/SetContentWithDrive branch November 4, 2016 21:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

WG-Cmdlets general cmdlet issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants