#PSDSC team have opened a survey to get feedback on what YOU want from DSC: https://t.co/I96FqTWiVB
@migreene published a recent blog on the latest DSC plans: https://t.co/NLCxWRaQzD
Learn more about our new Policy service here: https://t.co/ljnBuNc60o
#PowerShell#Azure
#DscResourceKit community call is this Wednesday March 27 at 12PM PACIFIC time. There is a new link for the call so that the meeting can be recorded. We are also switching to a Teams meeting. NEW LINK: https://t.co/9f2bZMi38C
#DscResourceKit community call is today at 12PM (PACIFIC TIME) (in 30 minutes from this tweet). Link is same as last time: https://t.co/6GZRDOUwKz #PSDSC#PowerShell
Reminder that the #DSCResourceKit community call is next week (due to all the holidays) on Wednesday January 9 at 12PM (PACIFIC TIME). Here is the (hopefully fixed) link to the call for next week: https://t.co/6GZRDOUwKz #PSDSC#PowerShell
#DSCResourceKit community call public link expired. I will post a new link, but the call today is cancelled since I can't get everyone together again :( Any interest in rescheduling this call or just wait for the next one? #PSDSC@migreene
Due to the US holiday, the #DSCResourceKit community call is moving to next week (on 11/28). It will be at 12PM PST per usual. This won't affect the release, so release will be going out the same day. #PSDSC
@NanaLakshmanan Workaround didn't work for me. I didn't have the variables he changed the names of. Solution for me was to update NuGet with a specific command and run a new session. All fixed now :)
#DSCResourceKit release currently blocked by an error from the Publish-Module cmdlet. Have reached out to PSGallery/PSGet team for help. Sorry :( This is similar to the error if anyone else knows a fix: https://t.co/yRkVtuuxKd