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

ConvertTo-Xml topic contains misleading information and is incomplete. #3310

Closed
6 tasks done
mklement0 opened this issue Nov 19, 2018 · 0 comments · Fixed by #5585
Closed
6 tasks done

ConvertTo-Xml topic contains misleading information and is incomplete. #3310

mklement0 opened this issue Nov 19, 2018 · 0 comments · Fixed by #5585
Assignees
Labels
area-utility Area - Microsoft.PowerShell.Utility module

Comments

@mklement0
Copy link
Contributor

mklement0 commented Nov 19, 2018

The ConvertTo-Xml help topic mistakenly suggests that ConvertTo-Xml is the in-memory counterpart to Export-Clixml, however:

  • It produces different XML representations,

  • which, if saved to a file, cannot be re-imported with Import-Clixml

Therefore, the topic should be improved as follows:

  • Clarify that the XML formats differ and there's (at least currently) no way to make ConvertTo-Xml emit CLIXML

  • Describe the actual format, ideally with examples of real-world tools that can consume this format.

See also: A feature suggestion to optionally make ConvertTo-Xml emit CLIXML:

Version(s) of document impacted

  • Impacts 6.next document
  • Impacts 6 document
  • Impacts 5.1 document
  • Impacts 5.0 document
  • Impacts 4.0 document
  • Impacts 3.0 document
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-utility Area - Microsoft.PowerShell.Utility module
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants