Need link to Microsoft.HyperV.PowerShell.VirtualMachine

[RichardMeadowsTC]

I need to know what can be done with Microsoft.HyperV.PowerShell.VirtualMachine. Where is the documentation for it?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0a3bf152-630f-3a0a-b309-929b0899a637
• Version Independent ID: 6b16356b-f935-5497-5c28-0a9d71a1fb51
• Content: Get-VM (hyper-v)
• Content Source: docset/windows/hyper-v/Get-VM.md
• Product: w10
• Technology: powershell-windows
• GitHub Login: @AndreaBarr
• Microsoft Alias: v-anbarr

[doctordns]

This object is returned from Get-VM. You can find details about what it contains by using Get-Member, like this:L

Get-VM * | Select-Object -First 1 | Get-Member

What else do you need to know?

[RichardMeadowsTC]

Every thing I need to know, I learn from debugger. I should not have to debug the code. Please get some real documentation. Richard Meadows From: Thomas Lee<mailto:notifications@github.com> Sent: Monday, February 10, 2020 3:32 PM To: MicrosoftDocs/windows-powershell-docs<mailto:windows-powershell-docs@noreply.github.com> Cc: Richard Meadows<mailto:richard_meadows_7@msn.com>; Author<mailto:author@noreply.github.com> Subject: Re: [MicrosoftDocs/windows-powershell-docs] Need link to Microsoft.HyperV.PowerShell.VirtualMachine (#1762) This object is returned from Get-VM. You can find details about what it contains by using Get-Member, like this:L Get-VM * | Select-Object -First 1 | Get-Member What else do you need to know? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#1762?email_source=notifications&email_token=AI5HOOD42SDCR2CVRRIBUJDRCHPZ5A5CNFSM4KRAQB52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELKWL4I#issuecomment-584410609>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AI5HOOGPQAYA4OL5UTI4ABTRCHPZ5ANCNFSM4KRAQB5Q>.

[doctordns]

The open-source documentation repo does a good job of documenting cmdlets as well as the objects within the .NET Framework and used by PowerShell. So if you want to find out more about the two object types emitted by Get-ChildItem, easy.

Other cmdlets, implemented by CDXML, return 'WMI objects' - a .net object which wraps the WMI Data. For those cmdlets, WMI documentation is reasonable albeit focused at the developer, not the IT Pro.

In your case, the object type is produced by the Hyper-V product team whose objects do not appear to have details documented explicitly. When you do need to use them (eg setting nested virtualization) there are details on how to do it.

With that said, I agree that It would be useful to have all the Hyper-V object types explicitly documented. But any detailed documentation would likely require product team input.

This page, though, is not where to fix this issue. Separate documentation is needed to solve the problem. I suggest this issue be closed and a new one opened along the lines of "Hyper-V Objects Need Documentation" and set out the specific object types that need to be documented.

[RichardMeadowsTC]

This page isn’t documentation for Get-VM? I expect and demand that it document what it is returning. Richard Meadows From: Thomas Lee<mailto:notifications@github.com> Sent: Monday, February 10, 2020 5:02 PM To: MicrosoftDocs/windows-powershell-docs<mailto:windows-powershell-docs@noreply.github.com> Cc: Richard Meadows<mailto:richard_meadows_7@msn.com>; Author<mailto:author@noreply.github.com> Subject: Re: [MicrosoftDocs/windows-powershell-docs] Need link to Microsoft.HyperV.PowerShell.VirtualMachine (#1762) The open-source documentation repo does a good job of documenting cmdlets as well as the objects within the .NET Framework and used by PowerShell. So if you want to find out more about the two object types emitted by Get-ChildItem, easy. Other cmdlets, implemented by CDXML, return 'WMI objects' - a .net object which wraps the WMI Data. For those cmdlets, WMI documentation is reasonable albeit focused at the developer, not the IT Pro. In your case, the object type is produced by the Hyper-V product team whose objects do not appear to have details documented explicitly. When you do need to use them (eg setting nested virtualization) there are details on how to do it. With that said, I agree that It would be useful to have all the Hyper-V object types explicitly documented. But any detailed documentation would likely require product team input. This page, though, is not where to fix this issue. Separate documentation is needed to solve the problem. I suggest this issue be closed and a new one opened along the lines of "Hyper-V Objects Need Documentation" and set out the specific object types that need to be documented. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#1762?email_source=notifications&email_token=AI5HOOCF3ZJHI7QQM3432D3RCH2LTA5CNFSM4KRAQB52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELK4KGQ#issuecomment-584434970>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AI5HOOFT4DCCRPGLRQJ2DDTRCH2LTANCNFSM4KRAQB5Q>.

[doctordns]

This page documents one cmdlet. You would need separate pages to document the individual objects across this module. Such documentation would need to come from the Hyper-V team and not the open source MS Docs team since the code is not open source.

This issue should be closed and a new one opened to document the objects. There are quite a few so this is not a small ask.

FWIW I am currently writing a book chapter about these cmdlets and I too would like these objects defined. But there are better ways of achieving it. Are you interested in helping?

And finally, this is an open source project. Demanding it do things is hardly ever likely to be helpful.

[RichardMeadowsTC]

Where is Microsoft. Have the died? Richard Meadows From: Thomas Lee<mailto:notifications@github.com> Sent: Tuesday, February 11, 2020 12:37 AM To: MicrosoftDocs/windows-powershell-docs<mailto:windows-powershell-docs@noreply.github.com> Cc: Richard Meadows<mailto:richard_meadows_7@msn.com>; Author<mailto:author@noreply.github.com> Subject: Re: [MicrosoftDocs/windows-powershell-docs] Need link to Microsoft.HyperV.PowerShell.VirtualMachine (#1762) This page documents one cmdlet. You would need separate pages to document the individual objects across this module. Such documentation would need to come from the Hyper-V team and not the open source MS Docs team since the code is not open source. This issue should be closed and a new one opened to document the objects. There are quite a few so this is not a small ask. FWIW I am currently writing a book chapter about these cmdlets and I too would like these objects defined. But there are better ways of achieving it. Are you interested in helping? And finally, this is an open source project. Demanding it do things is hardly ever likely to be helpful. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#1762?email_source=notifications&email_token=AI5HOOHHRLC7AZQ6RRAOTRTRCJPV7A5CNFSM4KRAQB52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELLSVLA#issuecomment-584526508>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AI5HOOHKLW4CEKYEL4A4WNDRCJPV7ANCNFSM4KRAQB5Q>.

[doctordns]

I have opened a new issue for this.

See: #1776

THIS issue (#1762) should be closed.

[AriFordsham]

this is an open source project

So Microsoft are turning to open source to document their commercial products?

[doctordns]

The documentation at docs.microsoft, and more recently learn.microsoft.com are indeed open-source projects. This allows the community to fix minor issues or make small improvements. I have issued a lot of PRs to fix grammar and spelling issues, add examples, and clarify the behaviour of PowerShell components. This makes a lot of sense to me!