Joel "Jaykul" Bennett

My feedback

  1. 169 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Active Directory » Management Tools  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett supported this idea  · 
  2. 114 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    survey  ·  Mark Gray responded

    Thanks for the feedback! I have personally heard this request from a number of customers. IMHO having the ability to use GMS accounts would be a quite useful in DSC configurations. If this is an important feature for you as well, vote it up so that we can appropriately prioritize it as we move forward.

    MarkG

    Joel "Jaykul" Bennett supported this idea  · 
  3. 200 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    19 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →

    After much discussion with Aaron Nelson and Chrissy LeMaire, and thanks to the enormous amount of support for this item, we’ve recognized that this is something we need to accomplish, one way or another.

    We don’t want to offer an ETA on this as the work is not well understood by our team yet, and no one currently has immediate bandwidth on starting that investigation. But I want to stress the fact that is an important ask that we’re taking seriously as a priority.

    In the meantime, it would be immensely useful if someone with expertise in the DataTable space could submit an RFC (basically a brief spec) to our PowerShell-RFC repository on GitHub. That way, we can have a discussion about what the design of a ConvertTo-DataTable cmdlet might look like before we dive in on an implementation. The process for doing so is located here: https://github.com/PowerShell/PowerShell-RFC/blob/master/RFC0000-RFC-Process.md#draft

    I…

    Joel "Jaykul" Bennett commented  · 

    Should probably be in the SQLPS module?

    Joel "Jaykul" Bennett supported this idea  · 
  4. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett commented  · 

    You just need to run:

    fsutil.exe behavior set disable8dot3 1

  5. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett supported this idea  · 
  6. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett supported this idea  · 
  7. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett supported this idea  · 
  8. 13 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  PowerShell » PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett shared this idea  · 
  9. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett commented  · 

    Technically, it just breaks everything _until_ it hits a loop (and if it doesn't hit one, it stops everything except the shell).

    It would be good to have the case where it's not in a loop mentioned though, specifically stating it will exit all the way through every function, module, script until hit hits a loop or the prompt.

  10. 7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  5 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett commented  · 

    This is not the same as #199 -- that's the installer, this is just "save."

    I believe the suggestion here is that perhaps Save-Script should *default* to downloading *only* the script, and should have a switch like -Recurse to included dependencies. The assumption being made is that people using Save-Script are *not* using it to save the file for install elsewhere, but merely to allow inspecting it.

    I'm curious about these two different use cases, and I think it's worth investigating which is most prevalent before deciding which behavior should be the default -- but I do think there regardless of the default, there needs to be a switch which provides the other behavior. Perhaps it's most logical to use the same `-SkipDependencyCheck` switch proposed for the installer.

    Joel "Jaykul" Bennett supported this idea  · 
    Joel "Jaykul" Bennett commented  · 

    I totally agree that it makes sense there should be an *option* to not also download all the modules. There's a good chance I already have them anyway, or will be deploying to somewhere where they're already installed.

  11. 16 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  4 comments  ·  PowerShell » PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett commented  · 

    Personally, I think it would be a bad idea (and a breaking change) for modules, but a great idea for scripts.

    Joel "Jaykul" Bennett supported this idea  · 
  12. 37 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » WinRM  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett supported this idea  · 
  13. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  1 comment  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett shared this idea  · 
  14. 9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett shared this idea  · 
  15. 16 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  14 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett commented  · 

    Wrong: serializing an array as an object with a value property that contains the correct json representation of the array.

    Wrong: serializing built-in properties of arrays (like "Length" or "IsReadOnly" or "Count") at all. The cmdlet correctly ignores the built-in "Length" property, but not the built in "Count" alias property which PowerShell adds.

    Wrong: being unable to round-trip simple arrays of strings and numbers

    Anyway. I'm done arguing this. I don't think even the original developer would have defended it as long as you have.

    It can't be used to serialize simple arrays provided by users to pass them to JSON APIs, because you can't count on them being serialized the way JSON requires arrays to be serialized, so I had to write my own ConvertTo-Json for my customers. That's frustrating, but I guess it's a selling point for my work...

    Joel "Jaykul" Bennett commented  · 

    PowerShell wraps things in PSObject whenever it chooses, and when dealing with objects that have been passed as parameters or on the pipeline, one cannot simply use the BaseObject -- care must be taken to do the right thing.

    The CliXML serializer ***does the right thing***

    The JSON serializer does NOT. You can see this is the case by simply testing the workaround I posted earlier (serialize to CliXml, then deserialize, and then convertto-json).

    Why are you still arguing that it is not wrong?

    @PetSerAl Your workaround in this last post is completely incorrect. First: it will only work to unwrap the first level of an object. Second: if the thing is a PSCustomObject (including anything returned by a remote session, or imported from CliXML, etc) you would throw away ALL of the information. You most certainly would NOT be able to access any of it's properties.

    Joel "Jaykul" Bennett commented  · 

    ConvertTo-Json should be as smart about PSObjects as ConvertTo-CliXml is.

    So essentially, my proposal is that ConvertTo-Json should work the way it does if you first pipe things through CliXml.

    For instance, compare these objects:

    [PsObject]$po = @("Foo",2)

    [PSObject[]]$po2 = @("Foo",2),@("Bar",4)

    Compare:

    ConvertTo-Json $po
    ConvertTo-Json $($po)
    ConvertTo-Json $po2
    ConvertTo-Json $($po2)

    Now do the same thing but first serialize them to clixml:

    function cvjson($io) {
    $TP = [IO.Path]::GetTempFileName()
    Export-CliXml -InputObject $io -LiteralPath $TP
    Import-CliXml -LiteralPath $TP | ConvertTo-json
    Remove-Item $TP
    }

    cvjson $po
    cvjson $($po)
    cvjson $po2
    cvjson $($po2)

    You will see that abusing the CliXml serializer properly unwraps PSObjects when serializing them, producing the correct expected output every time. P.S. I don't know why wrapping the PSObject in $() fixes the bug at one level, but it doesn't work recursively, only using the CliXml serialize does.

    Joel "Jaykul" Bennett shared this idea  · 
  16. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett commented  · 

    Why do aliases even have parameters. Shouldn't you have to go through .ResolvedCommand.Parameters (which, oddly, is correct)?

    I think this should get fixed, one way or the other.

    Joel "Jaykul" Bennett supported this idea  · 
  17. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  1 comment  ·  PowerShell » Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett commented  · 

    That is, about_Checkpoint-Workflow

    Joel "Jaykul" Bennett shared this idea  · 
  18. 16 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett supported this idea  · 
  19. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett shared this idea  · 
  20. 16 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    Joel "Jaykul" Bennett supported this idea  · 
← Previous 1 3 4

Feedback and Knowledge Base