Export-CliXml shouldn't require writing to a file #3898

Activity

1. mklement0 commented on May 31, 2017

   

   Michael Klement (mklement0)

   on May 31, 2017

   Contributor

   More actions

   Given how this distinction is handled in existing cmdlets (e.g., Export-Csv / ConvertTo-Csv), that would probably call for a new cmdlet named ConvertTo-CliXml, plus a matching ConvertFrom-CliXml.

   👍React with 👍9Reacted by Chad McCaffery, Jeff Hicks, Lee Dailey, Troy Campbell, Rain Sallow (/u/ta11ow), wisemoth, bwarren18, Flavio Vilante and Viajaz
2. Steve Lee (SteveL-MSFT)

   added

   Area-Cmdlets-Utility

   Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bug

   Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributors

   on May 31, 2017
3. RichardSiddaway commented on Jun 6, 2017

   

   RichardSiddaway

   on Jun 6, 2017

   More actions

   Struggling to see the use case for Clixml representation of a an object just in memory. The CliXml cmdlets, as I understand them, are about persisting objects
4. pcgeek86 commented on Jun 6, 2017

   

   Trevor Sullivan (pcgeek86)

   on Jun 6, 2017

   Author

   More actions

   There are many different places you might want to persist objects. The filesystem is just one place.

   👍React with 👍9Reacted by Don Cruickshank, Jay Miller, Rain Sallow (/u/ta11ow), wisemoth, Lyx, bender-the-greatest, Flavio Vilante, Viajaz and Roman Kuzmin 1967-2026
5. pldmgg commented on Oct 17, 2017

   

   Paul DiMaggio (pldmgg)

   on Oct 17, 2017

   More actions

   Just came across a decent use case for this...

   Environment variables currently on take strings, so storing a complex object as an environment variable is not really possible. But if Export-Clixml could export a string to an environment variable, then we could relatively easily use Import-Clixml to re-hydrate the object.
6. markekraus commented on Oct 17, 2017

   

   Mark Kraus (markekraus)

   on Oct 17, 2017

   Contributor

   More actions

   If this followed the convention of CSV, it would actually be better to have a ConvertTo-Clixml cmdlet as well as a ConvertFrom-Clixml One reason I could think of this as useful is to pass the persisting object to things other than files, such as network streams or as body data in HTTP without needing to write to a file first.

   👍React with 👍7Reacted by Troy Campbell, Michael Klement, Rain Sallow (/u/ta11ow), bender-the-greatest, Flavio Vilante, Viajaz and Thomas Lee
7. pcgeek86 commented on Oct 18, 2017

   

   Trevor Sullivan (pcgeek86)

   on Oct 18, 2017

   Author

   More actions

   Building on top of what Mark Kraus (@markekraus) mentioned, another use case would be sending the CLIXML off to a message queue for processing by a different consumer application. I should not have to write the CLIXML to disk, and then read it again, to accomplish this.

   👍React with 👍3Reacted by Michael Klement, Flavio Vilante and Viajaz
8. charlieschmidt commented on Oct 21, 2017

   

   Charlie Schmidt (charlieschmidt)

   on Oct 21, 2017

   Last edited by charlieschmidt

   More actions

   @powershell/powershell grabbing, if i can?

   Progress on this: https://github.com/charlieschmidt/PowerShell/tree/powershell-3898-convertfromto-clixml
   I'll get the tests & docs added this weekend and do a proper PR
9. Charlie Schmidt (charlieschmidt)

   added 2 commits that reference this issue on Jan 8, 2018

   ConvertTo-Clixml and ConvertFrom-Clixml cmdlets (to go with Export/Im…

   ...

   This issue will close once commit 980ef33 is merged into the 'master' branch.

   980ef33

   ConvertTo-Clixml and ConvertFrom-Clixml cmdlets (to go with Export/Im…

   ...

   This issue will close once commit a6e6c30 is merged into the 'master' branch.

   a6e6c30
10. Nillth commented on Oct 15, 2019

    

    Marc Collins (Nillth)

    on Oct 15, 2019

    Last edited by Nillth

    More actions

    As a simple workaround how about this...

    `$SerializedString = [System.Management.Automation.PSSerializer]::Serialize($Object)

    $BackToObject = [System.Management.Automation.PSSerializer]::Deserialize($SerializedString)`

    👍React with 👍6Reacted by phbits, bender-the-greatest, Flavio Vilante, Viajaz, Kevin Janssen and Roman Kuzmin 1967-2026

    ❤️React with ❤️1Reacted by Francis Mercier
11. mklement0 commented on Oct 15, 2019

    

    Michael Klement (mklement0)

    on Oct 15, 2019

    Last edited by mklement0

    Contributor

    More actions

    It's a viable workaround, but I wouldn't call it simple, because this behind-the-scenes type is neither widely known nor easy to remember.

    As an aside: Serialize() defaults to depth 1, whereas Export-CliXml defaults to depth 2.

    ❤️React with ❤️2Reacted by Francis Mercier and Luiz

    👀React with 👀3Reacted by Rain Sallow (/u/ta11ow), bender-the-greatest and Flavio Vilante
12. Shriram0908 commented on May 28, 2020

    

    Shri Ram K S (Shriram0908)

    on May 28, 2020

    Contributor

    More actions

    I like to work on this issue. I hope that the cmdlets are still needed.

    👍React with 👍3Reacted by Rain Sallow (/u/ta11ow), bravo-kernel and wisemoth
13. vexx32 commented on May 28, 2020

    

    Rain Sallow (/u/ta11ow) (vexx32)

    on May 28, 2020

    Collaborator

    More actions

    I see there was an old PR that never got merged and is now closed... but yeah we can still use this. Go for it! 🙂

    👍React with 👍3Reacted by Shri Ram K S, Jay Miller and bravo-kernel
14. foxx commented on Oct 22, 2022

    

    Cal Leeming (foxx)

    on Oct 22, 2022

    More actions

    First of all, thanks to everyone for getting this fixed.

    Are there any indications on which release this might land in?

    It's a drop in the ocean of the 3.2k open issues, but would be nice to get this issue closed out :)
15. doctordns commented on Jun 9, 2023

    

    Thomas Lee (doctordns)

    on Jun 9, 2023

    Collaborator

    More actions

    So far as I can tell, this PR has not been merged. I can't see any trace of it in either 7.4 preview 3 or a recent daily build.

    Are there folks that want to take this on and complete the PR? If not, we should close this.
16. God-damnit-all commented on Sep 15, 2023

    

    God-damnit-all

    on Sep 15, 2023

    Contributor

    More actions

    So far as I can tell, this PR has not been merged. I can't see any trace of it in either 7.4 preview 3 or a recent daily build.

    Are there folks that want to take this on and complete the PR? If not, we should close this.

    Shri Ram K S (@Shriram0908) disappeared right before the finish line, it seems. 😕
17. microsoft-github-policy-service

    added

    In-PRIndicates that a PR is out for the issueIndicates that a PR is out for the issue

    on Jan 6, 2024
18. ArmaanMcleod commented on Jan 6, 2024

    

    Armaan Mcleod (ArmaanMcleod)

    on Jan 6, 2024

    Contributor

    More actions

    So far as I can tell, this PR has not been merged. I can't see any trace of it in either 7.4 preview 3 or a recent daily build.

    Are there folks that want to take this on and complete the PR? If not, we should close this.

    Thomas Lee (@doctordns) I've created a new PR which should address this. Will wait for feedback and hopefully get this one merged since I needed this recently and would be great to have these cmdlets in 7.4.
19. Ilya (iSazonov)

    closed this as completedin #21063on Jul 26, 2024
20. microsoft-github-policy-service commented on Jul 26, 2024

    

    microsoft-github-policy-servicebot

    on Jul 26, 2024 – with Microsoft GitHub Policy Service

    Last edited by unfurl-links

    Contributor

    More actions

    📣 Hey Trevor Sullivan (@pcgeek86), how did we do? We would love to hear your feedback with the link below! 🗣️

    🔗 https://aka.ms/PSRepoFeedback

    Microsoft Forms
21. Ryan Yates (kilasuit)

    added

    WG-Cmdletsgeneral cmdlet issuesgeneral cmdlet issues

    and removed

    WG-Cmdlets-Utility

    on Jul 17, 2026