Anonymous

My feedback

  1. 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 » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  2. 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 » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  3. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    I wish I could edit the title/post. Realized I should have clarified this being about evaluation for intellisense.

    An error occurred while saving the comment
    Anonymous commented  · 

    Another simple example showing intellisense could be more helpful for paths with spaces.

    # intellisense shows dynamic params -Attributes, -Directory, etc
    Get-ChildItem C:\Windows

    # intellisense does not show dynamic params
    Get-ChildItem 'C:\Program Files'

    Anonymous shared 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

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

    Thanks for the feedback!

    We will take this into consideration in a future release.

    MarkG

    An error occurred while saving the comment
    Anonymous commented  · 

    It seems like improving the Service resource would be a better option than writing a new one that could install/uninstall a service, make sure it pointed to the correct path, runs as the proper account, has the right startup type, etc - since the Service resource already does all those things. It would be nice for the end-user to choose which attributes of the service were in the desired state, just like startup type is an optional attribute.

    There's also no indication in the documentation (https://msdn.microsoft.com/en-us/powershell/dsc/serviceresource) that state has a default value, and it's listed as optional.

    Anonymous shared this idea  · 

Feedback and Knowledge Base