See example in PR dsccommunity/ActiveDirectoryDsc#600.

There are some duplicated code that could be removed to simplify the resource.

Instead of calling Get-ADObject here we could instead call Get-TargetResource.

https://github.com/PowerShell/ActiveDirectoryDsc/blob/c3c93ba1bc1b8168655cc971474dde277d7c9574/DSCResources/MSFT_ADServicePrincipalName/MSFT_ADServicePrincipalName.psm1#L95

Instead of having this code

https://github.com/Power

Details of the scenario you try and problem that is occurring:
For a large search topology I'm missing a few things. One is that all the databases are created in the same sql instance. The name cannot be configured individually and there is only one property for the sql server. And I need to create multiple crawl store databases which is not possible with the current version. The multiple cra

We should add the build task Generate_Conceptual_Help to create conceptual help.
https://github.com/dsccommunity/DscResource.DocGenerator#generate_conceptual_help

DSC resource MSFT_PackageResource failed to execute Set-TargetResource functionality with error
message: Package from************************* was installed, but the specified
ProductId and/or Name does not match package details

Is there a way to make ProductID not required as even after the install the DSC config status remains as failed, when we leave the product ID blank.

Details of the scenario you tried and the problem that is occurring

When you specify an application pool that does not exist in a xWebsite resource, the resource does not check if the specified application pool exists. This results in a broken website with error "Unknown:The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)"

Verbose logs showin

Details of the scenario you tried and the problem that is occurring:
In the resource CertificateImport there should be no need to have the non-mandatory parameter Ensure in the Get-TargetResource function.

https://github.com/PowerShell/CertificateDsc/blob/6906fc5b31a783a899260c9c9d4ba84a02dd4c14/Modules/CertificateDsc/DSCResources/MSFT_CertificateImport/MSFT_CertificateImport.psm1#L65-

Details of the scenario you tried and the problem that is occurring:
Suggest we add a read-only parameter to the WaitForVolume resource. That way the Get-TargetResource could call Test-TargetResource and return the result (the actual current state) of the volume in the property Available when calling Get-DscConfiguration.

**The DSC configuration that is using the resource (as detai

The other tests are using a pattern to use different stub modules. This unit test does not.

Verbose message string should be added as a localized string.

https://github.com/dsccommunity/DscResource.DocGenerator/blob/6486a706623c2f7816609355f913d7ab93545ad0/source/Public/New-DscResourcePowerShellHelp.ps1#L110