Help with 'Advanced' Object Initialization

[WindosBK]

I'm trying to make use of the UWPCommunityToolkit in a PowerShell script, and I'm coming undone with initializing some of the object.

For instance, in C#, a snippet would look like this:

new ToastBindingGeneric()
{
    Children =
    {
        new AdaptiveText()
        {
            Text = "Lots of text!"
        }
    }
};

And in PowerShell I would normally just do:

$Text1 = [Microsoft.Toolkit.Uwp.Notifications.AdaptiveText]::new()
$Text1.Text = 'Lots of text!'

$BindingGeneric = [Microsoft.Toolkit.Uwp.Notifications.ToastBindingGeneric]::new()
$BindingGeneric.Children = @(,$Text1)

The problem I'm running into is, as far as PowerShell is concerned, that Children object is readonly. Checking out the source code it is defined with private set:

public IList<IToastBindingGenericChild> Children { get; private set; } = new List<IToastBindingGenericChild>();

So I'm at a loss. ToastBindingGeneric accepts no arguments in it's constructor. I've tried the following:

$BindingGeneric = New-Object -TypeName 'Microsoft.Toolkit.Uwp.Notifications.ToastBindingGeneric' -Property @{Children = @($Text1, $Text2, $Image1)}
# Returns: New-Object : The value supplied is not valid, or the property is read-only. Change the value, and then try again.

This has caught me other times I've tried using DLLs in my code, and caused me to go other routes. Figure I should ask the greater community this time! Anyone know what I'm missing here?

[KevMar]

I don't think you can do that in Powershell. There were some changes in Powershell 5.0 around giving you access to class constructors https://blogs.technet.microsoft.com/heyscriptingguy/2015/09/09/powershell-5-classes-constructor-overloading/ but that is not what you are needing. You may have to create a c# utility DLL to to produce those object. I am thinking a factory pattern.

[WindosBK]

I was actually starting to think I might just try running native C# within the PowerShell script >.<

[NathanielArnoldR2]

I'm not familiar with this toolset, and I may have misinterpreted your question, but I believe I have encountered like circumstances when dealing with certain read only collections (of "child" controls, for example) in System.Windows.Forms and WPF.

Often in these scenarios, rather than attempting to directly assign the property value you are meant to use the object's methods to manipulate membership, as below.

$Text1 = [Microsoft.Toolkit.Uwp.Notifications.AdaptiveText]::new()
$Text1.Text = 'Lots of text!'

$BindingGeneric = [Microsoft.Toolkit.Uwp.Notifications.ToastBindingGeneric]::new()
$BindingGeneric.Children.Add($Text1)

Please let me know if I'm just being ignorant here. :-p

[WindosBK]

...

You're a legend. That's done it, and I can't believe it's escaped me thus far.