Warren F.

My feedback

  1. 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 » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. supported this idea  · 
  2. 31 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Security and Assurance » Misc  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. supported this idea  · 
  3. 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 →
    Warren F. supported this idea  · 
  4. 12 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 » Package Management  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. supported this idea  · 
  5. 28 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 →
    Warren F. supported this idea  · 
    Warren F. commented  · 

    Agreed. Although, not sure how it could be included. Maybe as a module in Windows PowerShell, included (a la Pester), but also available in the Gallery for use with PowerShell Core (on Windows), or down-level systems?

    This module from Shay works everywhere, and has been around a while. It might be a good start https://psremoteregistry.codeplex.com/.

    Also: Providers should never be the sole way to access something. IMHO we should see the following progression:

    * API
    * Module/Cmdlets
    * Provider

    Providers are often even more abstracted than Cmdlets, to a point where the Registry provider is IMHO *too* abstract. What does an item correspond with? An itemproperty? It's a cool trick, browsing like the filesystem, but when folks need to actually extract data and change data, you find confusion. Oh... And no remote capabilities outside of using inside a pssession? Working with the registry in PowerShell outside of modules like Shay's is frustrating, and I say this as someone with 6 years writing PowerShell - imagine someone starting out.

    Apologies for the wall of text. This has been a thorn for a while : )

  6. 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…

    Warren F. commented  · 

    Voted. Makes sense to me. Yes, SQL Server is a common use case, but as Chrissy and others have mentioned, this is a generic construct that many folks find handy for other scenarios, e.g.:

    * In memory database-esque usage
    * Integration with various database systems and other technologies that can work with datatables

    Lastly - IMHO every new function added to PowerShell (with rare exceptions) should be included in a module, allowing folks to install / import it as needed. This case in particular, where the code could easily work down-level, should be included in a module that folks with older PowerShell versions could use. That said, with core functionality like this, even if it's a module, IMHO it would be better handled by the PowerShell team, or another Microsoft team (with the help from the OSS community, of course)

    Cheers!

    Warren F. supported this idea  · 
  7. 222 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  PowerShell » Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. commented  · 

    Both, IMHO prioritizing examples first. Like Martin said, on top of value as examples, folks can often imply syntax from those examples.

    Warren F. commented  · 

    Ping! This would be crazy helpful. Probably the reason it was the top Connect entry for PowerShell. A conversion tool that takes arbitrary C# snippets and translates to PowerShell might be a handy way to solve this, while also providing a tool end-users could use for other non-MSDN examples out there.

    Cheers!

    Warren F. supported this idea  · 
  8. 437 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  Core Server » Roles & features  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. supported this idea  · 
  9. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    investigating  ·  3 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. supported this idea  · 
  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 →
    Warren F. supported this idea  · 
  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 →
    Warren F. commented  · 

    I'm not tied to any implementation, but to address Joel's comment, my original thought was as follows:

    Today:
    * UserA publishes GenericModuleName
    * UserB can't publish GenericModuleName
    * Install-Module install's UserA's GenericModuleName

    Goal:
    * UserA publishes GenericModuleName (first)
    * UserB publishes GenericModuleName (second)
    * Install-Module GenericModuleName installs UserA's module due to publication date
    * Install-Module UserB/GenericModuleName (or, Install-Module GenericModuleName -Author UserB) installs UserB's module

    If I need both modules on a machine, I can still Save-Module or use different scopes, or, at some point ideally, virtual environments...

    Cheers!

    Warren F. shared this idea  · 
  12. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    Have to investigate this a bit. I believe there are several different download/install approaches. Question back to you: what would be the top 3-5 download areas you would want to see?

    Warren F. shared this idea  · 
  13. 7 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 →
    Warren F. supported this idea  · 
  14. 18 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 » Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. supported this idea  · 
  15. 59 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. supported this idea  · 
  16. 9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. supported this idea  · 
  17. 25 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 » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. supported this idea  · 
  18. 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 » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. supported this idea  · 
  19. 64 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →
    Warren F. supported this idea  · 

Feedback and Knowledge Base