Local build fails with errors

[dsccommunity]

Local build fails with errors

[raandree]

I have tested the build on a newly created Windows Server 2019 machine in Azure and all worked fine.

After the successful build, for example the AuditPolicies DSC Configuration existed:

$dscResources = Get-DscResource -Module CommonTasks
$dscResources.Name -contains 'AuditPolicies' #returned true

The integration tests for this particular resource looked fine and I do have a file names localhost_AuditPolicies.mof in the output folder:

Describing 'AuditPolicies' DSC Resource compiles
    [+] 'AuditPolicies' compiles 19.09s
    [+] 'AuditPolicies' should have created a mof file 3ms

Do you have the DSC Resource module AuditPolicyDsc somewhere in the PSModulePath additionally to output\RequiredModules?

[gaelcolas]

One way to troubleshoot this is to create a short Config script that uses the missing resource and let it throw all its errors.
As Raimund pointed out, this issue is usually an issue with some PSModulePath.
Probably worth checking the version of Sampler in use, as if an old version is already loaded/available, it may not bootstrap to a version "new enough".

[stehlih]

I have checked my PSModulePath and in my private module path I found installed versions of AuditPolicyDsc and SecurityPolicyDsc. But here are the same versions installed as downloaded by PSDepend from the CommonTasks build.

The reason of the problem are different versions of nuget.exe. The existing versions of AuditPolicyDsc and SecurityPolicyDsc in my private module path were downloaded with NuGet 5.7.0 in February 2021. Now PSDepend downloads a new NuGet 6.0.0. The generated PSGetModuleInfo.xml for each module has a different structure and this is the cause of the error.

[raandree]

Thanks @stehlih, as expected. Maybe when compiling the MOFs we can save, change for the compile time and restore the PSModulePath to prevent these conflicts in the future.