Skip to content
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

Allow ConvertTo-Xml to emit CLIXML (the same XML format as Export-Clixml) #8311

Open
mklement0 opened this issue Nov 19, 2018 · 2 comments

Comments

Projects
None yet
4 participants
@mklement0
Copy link
Contributor

commented Nov 19, 2018

Summary of the new feature/enhancement

Follow-up from #8308 (comment), quoting @SteveL-MSFT:

Ideally, it seems like we should have had ConvertTo-Xml take a -Format parameter that supported CliXml and other xml formats rather than having this confusion between ExportTo-CliXml and ConvertTo-Xml having incompatible xml formats.

Note that the documentation is lacking, as of this writing, as it mistakenly suggests that ConvertTo-Xml is the in-memory equivalent of Export-CliXml - see MicrosoftDocs/PowerShell-Docs#3310

Update: Adding dedicated ConvertTo-CliXml and ConvertFrom-CliXml cmdlets has been requested and green-lit (#3898), though the associated PR has gone stale: #5815

In light of that, it may be better to leave ConvertTo-Xml alone and simply fix / amend its documentation.

@SteveL-MSFT

This comment has been minimized.

Copy link
Member

commented Jan 1, 2019

Marking as First-Time-Issue as I think this should be relatively straight forward to add a parameter and have it use some of the internal APIs used by Export-CliXml to do the conversion.

@ece-jacob-scott

This comment has been minimized.

Copy link
Contributor

commented Feb 23, 2019

Hack Illinois participant
Working with @rjmholt and @TylerLeonhardt

I will take this one on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.