Micah Rairdon
My feedback
-
98 votes14 comments · PowerShell » Desired State Configuration (DSC) · Flag idea as inappropriate… · Admin →
Justin,
We totally understand that a robust Pull server / central management solution is something that is critical to your success with DSC. We have invested quite heavily in Azure Automation DSC (AA DSC) to fill many of these needs. With that said, I would be very interested to understand if the AA DSC solution does not work for you (and other customers) and why? Vote and comment if this is important to you.
Also interesting feedback on our ‘bad ideas’. Thanks!
MarkG
Micah Rairdon
supported this idea
·
-
39 votesMicah Rairdon
supported this idea
·
-
224 votes
https://github.com/dotnet/docs/issues/3455 The DotNet team is collecting feedback on this item as well.
An error occurred while saving the comment Micah Rairdon
supported this idea
·
-
4 votesMicah Rairdon
supported this idea
·
-
11 votesMicah Rairdon
supported this idea
·
-
37 votesMicah Rairdon
supported this idea
·
-
148 votesMicah Rairdon
supported this idea
·
-
3 votes
Not critical, but definitely annoying. I’ve filed a bug internally.
Micah Rairdon
supported this idea
·
-
146 votesMicah Rairdon
supported this idea
·
-
140 votes
Your votes on this and other features helps us in our feature prioritization.
Thank you!!
MarkG
Micah Rairdon
supported this idea
·
-
37 votesinvestigating · 2 comments · PowerShell » Desired State Configuration (DSC) · Flag idea as inappropriate… · Admin →Micah Rairdon
supported this idea
·
-
57 votes
This is a very difficult thing to implement, it could potentially break many of the add-ons, and could introduce some very confusing UI elements.
That said, we’re interested to get more ideas from you for how something like this might work. Feel free to post your comments below.
Thanks,
JoeyMicah Rairdon
supported this idea
·
-
80 votes
Hi John,
We’d like to do this at some point. We’ll post back here if it happens in the ISE Preview. Read more about it here: https://blogs.msdn.microsoft.com/powershell/2016/01/20/introducing-the-windows-powershell-ise-preview/
Thanks,
JoeyMicah Rairdon
supported this idea
·
-
64 votes
Hi Jason,
We definitely consider this hugely valuable, but it is a big work item, and we’re not sure where it sits in our current roadmap.
We’ll post back here as more details become available.
Thanks,
JoeyMicah Rairdon
supported this idea
·
-
153 votes
Hi all,
This work has already been started and will likely ship with a future version of the PowerShell ISE Preview. Read more about the Preview here: https://blogs.msdn.microsoft.com/powershell/2016/01/20/introducing-the-windows-powershell-ise-preview/
Thanks,
JoeyMicah Rairdon
supported this idea
·
-
5 votesMicah Rairdon
supported this idea
·
-
117 votes
Hi everyone,
With PowerShell 6.0, we’ve already begun updating our versioning system to be more descriptive. Right now, PSVersion returns 6.0.0-alpha as a System.Management.Automation.SemanticVersion object (with Major, Minor, Patch, and Label properties), and we’ve also added a GitCommitId property to PSVersionTable that matches perfectly with tags on GitHub: https://github.com/powershell/powershell/tags
Still, we can definitely continue to improve the semantic version implementation. You can track (and contribute to!) the discussion on these improvements here: https://github.com/PowerShell/PowerShell/issues/2354
Thanks,
JoeyMicah Rairdon
supported this idea
·
-
2 votesMicah Rairdon
supported this idea
·
-
3 votesMicah Rairdon
supported this idea
·
-
10 votesMicah Rairdon
supported this idea
·
Both. Examples more useful to me.