xDSCResourceDesigner
xDSCResourceDesigner copied to clipboard
Work need to be done to convert this repository to use the new CI pipeline. https://dsccommunity.org/blog/convert-a-module-for-continuous-delivery/
#### Pull Request (PR) description This PR changes the resource output files produced by the `New-xDscResource` function to use ASCII encoding instead of Unicode to conform to the [Dsc style...
#### Pull Request (PR) description This PR changes the quotes used around validate set values to be single quotes instead of double quotes to conform to [Dsc Resource Style Guidelines](https://github.com/PowerShell/DscResources/blob/master/StyleGuidelines.md#correct-use-of-single--and-double-quotes)...
The Update-xDscResource command seems to ignore the next-to-last line of the Resource .psm1 file that it's updating. For example, just as a demonstration, change the "*" in the Export-ModuleMember line...
It would be useful if you did not require having administrator privileges to create a resource. I'm in a situation where I would like to create a module that I...
MOF strings have escaping rules that are not honored by the current xDSCResourceDesigner implementation, which can cause xDSCResourceDesigner to create MOF files with syntax errors. For example: ``` powershell New-xDscResourceProperty...
The use case for this is when a configuration is in the pending state and doesn't exit; such as occurs when a resource is stuck on an external resource or...
You could include best practice warnings like not setting boolean defaults or setting defaults on mandatory parameters. Daren
I'm writing a C# resource and consequently do not need the generated `.psm1` file - only the `.schema.mof` file.
Wonderful toolset, but it assumes you are using PowerShell to author your custom resources. Can the tools be updated to support C# authoring/testing?