LUVoice

My feedback

  1. 21 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  General Feedback » Applications & Add-ons  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice supported this idea  · 
    LUVoice commented  · 

    Vital product for us. A little buggy on the deployment side occasionally.

    One support/enhancement request - to be able to copy text from the Comments field, of selected history line, in the GPO History window.

  2. 2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General Feedback » Bug  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice supported this idea  · 
  3. 2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General Feedback » Bug  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice supported this idea  · 
  4. 3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General Feedback » Shell, GUI, & Explorer  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice shared this idea  · 
  5. 2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  2 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice commented  · 

    If there's other characters in the string it should work as a string. If "0" is by itself then should work like a variant.

    LUVoice supported this idea  · 
  6. 6 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice commented  · 

    it's a property of EchoArgs and numerous other EXEs such as REG and FINDSTR. May be they are compiled from the same language that treats Argv the same way by default?

    What happens if you use:

    & EchoArgs "C:\spaces and trailing slash\\" more args

    EchoArgs isn't part of Powershell proper (not v3 on Win 7, at least), so bugs/behaviour in EchoArgs might not be dealt with here.

  7. 9 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice commented  · 

    If you really want colons, can put "mm\:ss" or "mm':'ss".

    Ref: https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings

  8. 2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice commented  · 

    Oh, and if it happens, I just do Ctrl+Z straight away to get it back, and try again.

    LUVoice commented  · 

    If I drag the line to exactly the first character position of the destination, I get a good copy.

    If I am lazy and drag the line to over the number left of the destination, it's gone. nada, deleted. In other editor I use regularly it is more forgiving.

    This is soooo annoying!

    LUVoice supported this idea  · 
  9. 56 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice supported this idea  · 
  10. 78 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice supported this idea  · 
  11. 162 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice supported this idea  · 
    LUVoice commented  · 

    I think it should be a separate function, not just Copy-Item. Perhaps Invoke-NtfsSync? Might be useful, though, to also supplement Copy-Item with some Robocopy smarts when copying NTFS to NTFS. Stepping back ... a new more robust filesystem for Windows may be just around the corner ... May need to consider uniting BITS and Robocopy functionality in new command(s). Just some thoughts.

    LUVoice commented  · 

    Please can a 'validate' function be included? It might be prioritized after the like-for-like functionality, but I'm sure an optional parameter to 'validate' transferred data would be valuable.

  12. 6 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice supported this idea  · 
  13. 2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice supported this idea  · 
  14. 5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice supported this idea  · 
  15. 28 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice commented  · 

    This request would work well with remembering state of collapsed regions/functions/etc. Also see (and vote if you like):

    https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/12523590-presist-the-state-of-collapsed-regions-functions-e

    LUVoice commented  · 

    Funnily enough, a crashed powershell ISE session will re-open previously open documents. So, yeah, why not preserve this information on normal closure?

    (There was a bug, though, when a crash recovery happened to me recently - the session/file which I had originally opened in standard user context (no elevation) recovered in High integrity level (aka elevated/admin), but the session/files which I had originally opened in elevated mode recovered in Medium integrity level (aka standard user mode). Am logging it as a separate bug. Need to consider this issue for normal ISE closure/re-opening, too.

    LUVoice supported this idea  · 
  16. 5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice commented  · 

    ISE persist state - would work well with remembering open files - also see (and vote if you like):

    Windows PowerShell ISE: Add ability to save/load session state
    https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/11087943-windows-powershell-ise-add-ability-to-save-load-s

    LUVoice supported this idea  · 
  17. 1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice shared this idea  · 
  18. 2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice commented  · 

    Thank you, just had a look, that's a great module - already thought of everything - except that it needs to be pre-installed and pre-loaded. And (although I will use that module in my own profile) I was hoping that something could operate without any thoughtful preparation - eg when we are supporting other 'clean' machines with default Powershell configuration.

    LUVoice shared this idea  · 
  19. 1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →
    LUVoice commented  · 

    Having said that, being able to emulate powershell 2, 3 or 4 in PS 5 could be useful in our dynamic environment. Eg When in v3 emulation mode, reject v4 or v5 syntax.

  20. 13 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →

    It would certainly be cool, but we’re not really investing in Out-GridView at this point in time. I’ll leave this open as a Survey to see if the demand surpasses our bar (though I’d caveat that demand would have to be fairly high).

    Thanks,
    Joey

    LUVoice supported this idea  · 
← Previous 1

Feedback and Knowledge Base