Create RegistrySetting object with PowerShell

In the comment of the blog “Creating a SCCM 2012 Application” Adam asked the question if it could be expanded with adding Enhanched detection method. Because there isn’t still a good SDK I started to do a little research.I found a great post from Adam Meltzer (link).

Although it is C# it’s easy to translate it to PowerShell. But there I was wrong. I translated this C# command

RegistrySetting registrySetting = new RegistrySetting(null);

to

$registrySetting = New-Object Microsoft.ConfigurationManagement.DesiredConfigurationManagement.RegistrySetting($null)

But then I get the following error just as described in this post (link)
New-Object : Constructor not found. Cannot find an appropriate constructor for type Microsoft.ConfigurationManagement.DesiredConfigurationManagement.RegistrySetting.

After lots of troubleshooting I discoverd that this is an error in de DcomObject.dll. In C# this command works but in PowerShell it fails. I also discoverd a simple workaround. I created a custom dll that creates the object and function that can be called from powershell to get the empty RegistrySetting object.

The following command should be run to get an empty RegistyrSetting object

[System.Reflection.Assembly]::LoadFrom("$PATH\RegistrySetting.dll")
$temp = New-Object RegistrySettingNamespace.RegistrySettingRob ""
$registrysetting = $temp.GetRegistrySetting()
$registrysetting

Location : HKEY_LOCAL_MACHINE\
RootKey : LocalMachine
Key :
ValueName :
IsValueNameRegularExpression : False
Is64Bit : False
CreateMissingPath : True
SupportedMethods : {Value, Count}
IncludeDcmDigestAsNamespace : False
Annotation : Microsoft.SystemsManagementServer.DesiredConfigurationManagement.Rules.Annotation
SettingDataType : Microsoft.SystemsManagementServer.DesiredConfigurationManagement.Expressions.ScalarDataType
Name :
SourceType : Registry
ParentConfigItem :
LogicalName : RegSetting_6186aeeb-1013-4e14-acb7-f4a72495dac1
Applicability :
SettingOptimization :
Description :
ApplicableAtUserLogon : False
IsDirtyExposed : False
SupportsRemediation : True

It is not the most beautiful solution but until this bug is solved its the only solution to work with the RegistrySetting object in PowerShell

********************************
Update
********************************
The previous version only worked with the DcomObject.dll found in SCCM 2012 SP1. So therefore I added also the .cs file and the steps to compile the custom dll. A prerequisite to compile is of course having a visual studio edition installed. The new zip file can be found below

RegistrySetting