![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | Export-CliXml/Export-Csv: Change to Export-Object? I'd like to suggest that these two Export cmdlets (and their corresponding importers) be consolidated into Export-Object/Import-Object cmdlets. It would reduce verb confusion. We have Export-Alias and Export-Console, where the noun clearly indicates what is being exported. With Clixml and Csv, we are specifying the format of the export. It's a good Less Is More modification. The generic Object noun is already used for object manipulation, so people are likely to guess that this is the right noun for export/import. Specific formats can then be handled by a -Format or -As parameter. Opinions? |
My System Specs![]() |
| | #2 (permalink) |
| | Re: Export-CliXml/Export-Csv: Change to Export-Object? This is a good suggestion. Please submit it. -- Jeffrey Snover [MSFT] Windows PowerShell Architect Microsoft Corporation This posting is provided "AS IS" with no warranties, no confers rights. "Alex K. Angelopoulos [MVP]" <a k a @ m v p s . o r g> wrote in message news:Ol0Nx2%23hGHA.3904@TK2MSFTNGP02.phx.gbl... > I'd like to suggest that these two Export cmdlets (and their corresponding > importers) be consolidated into Export-Object/Import-Object cmdlets. > > It would reduce verb confusion. We have Export-Alias and Export-Console, > where the noun clearly indicates what is being exported. With Clixml and > Csv, we are specifying the format of the export. > > It's a good Less Is More modification. The generic Object noun is already > used for object manipulation, so people are likely to guess that this is > the right noun for export/import. Specific formats can then be handled by > a -Format or -As parameter. > > Opinions? > |
My System Specs![]() |
| | #3 (permalink) |
| | Re: Export-CliXml/Export-Csv: Change to Export-Object? https://connect.microsoft.com/feedba...5769&SiteID=99 "Jeffrey Snover [MSFT]" <jsnover@microsoft.com> wrote in message news:OU1K7z$hGHA.764@TK2MSFTNGP03.phx.gbl... > This is a good suggestion. Please submit it. > > -- > Jeffrey Snover [MSFT] > Windows PowerShell Architect > Microsoft Corporation > This posting is provided "AS IS" with no warranties, no confers rights. > "Alex K. Angelopoulos [MVP]" <a k a @ m v p s . o r g> wrote in message > news:Ol0Nx2%23hGHA.3904@TK2MSFTNGP02.phx.gbl... >> I'd like to suggest that these two Export cmdlets (and their >> corresponding importers) be consolidated into Export-Object/Import-Object >> cmdlets. >> >> It would reduce verb confusion. We have Export-Alias and Export-Console, >> where the noun clearly indicates what is being exported. With Clixml and >> Csv, we are specifying the format of the export. >> >> It's a good Less Is More modification. The generic Object noun is already >> used for object manipulation, so people are likely to guess that this is >> the right noun for export/import. Specific formats can then be handled by >> a -Format or -As parameter. >> >> Opinions? >> > > |
My System Specs![]() |
| | #4 (permalink) |
| | Re: Export-CliXml/Export-Csv: Change to Export-Object? "Alex K. Angelopoulos [MVP]" <a k a @ m v p s . o r g> wrote in message news:OUm5BiCiGHA.2188@TK2MSFTNGP04.phx.gbl... > https://connect.microsoft.com/feedba...5769&SiteID=99 > I like it. Voted. -- Keith |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Export-clixml producing weird xml output | PowerShell | |||
| Formatting Inline for Export-CliXML Command | PowerShell | |||
| Export/Import-CliXml oddity | PowerShell | |||
| export-clixml and compare-object question | PowerShell | |||
| Export-Clixml output is inconvenient for viewing | PowerShell | |||