ll.c | A Linked List library for C | Functional Programming library

The .accessPackageAssignmentPolicies property contains an array ([...]-enclosed in the JSON input).

Even though that array happens to contain only one element, you still need to access it by index in order to set its (only) element's properties; e.g.:

Your command actually succeeded(!) in principle, as evidenced by the wording of the error message.

If all you want to do is to set the local-machine policy for future sessions, you can simply ignore the error, by enclosing the statement in try / catch; also note the trailing ; exit 0 so as to ensure that exit code 0 is reported back to Ansible:

I believe the comments have been explanatory, the grouping operator (..) is necessary not only for precedence but also, as demonstrated in the example from the Doc, it allows you to let output from a command participate in an expression.

Without it, PowerShell interprets -eq as a parameter of the function mj and 23 as an argument for said parameter.

You can test this by adding $args or a parameter that takes ValueFromRemainingArguments to your function:

What a nightmare! but I got it working for both 1809 and 20h2.

F# has a mechanism for defining extensions that is "C#-compatible", and your use case is specifically called out, check here.

Something like this should work:

Did you configure domain wide delegation? Even if the impersonation and everything may be correct, without domain wide delegation the service account does not get enough permissions and can show this error.

Answer modification: The problem is actually related to the user impersonation as it is not being performed correctly in the code.

I tested your example in 2013-32 with an empty class v with the 100 properties, and only got a small difference in timings. I can only assume something related with your particular setup.

However I'd say your 0.45 sec is slow even in an old system, and the reason for that is your particular use of a large Collection. Two ways to improve -

1. Counter intuitively with large collections it's much faster to use Keys rather than Indexes to retrieve items, populating is only slightly slower with keys. Referencing col.Item(1) is fast but bigger indexes are progressively slower, seems internally the collection is looped to find the given index each time ...

Without showing actual code and giving a more descriptive detailing about what's going on aside from "it doesn't work" it's difficult to say exactly what is occurring here but I'll do my best.

Thankfully, according to Microsoft's documentation you most certainly can run the Powershell SDK in a self-contained .Net application.

A self-contained .NET application can use Microsoft.PowerShell.SDK to run arbitrary PowerShell functionality without depending on any external PowerShell installations or libraries.

This leads me to believe that you may not be having an issue with the SDK itself but rather with the compiler.

Single-File deployments

I noticed in your screenshot that you are attempting to perform a single-file deployment. You could potentially be having a few issues here. One is to ensure that you're not using an incompatible API. If you are calling any of these within your application, that could be a factor:

• Assembly.CodeBase
• Assembly.EscapedCodeBase
• Assembly.GetFile
• Assembly.GetFiles
• Assembly.Location
• AssemblyName.CodeBase
• AssemblyName.EscapedCodeBase
• Module.FullyQualifiedName
• Module.Name

As none of these are compatible with single-file deployments.

Trimming

Another issue you may be experiencing is referred to as trimming. This is where the compiler will 'trim' unused assemblies from the project at compile time and tends to happen on release runs. While I believe this is off by default you can add the following to your .csproj file to ensure that trimming is disabled:

As Santiago Squarzon has mentioned ForEach-Object -Parallel was introduced in PowerShell 7.0 Preview 3 , so If you are using Powershell ISE it will be of Version 5.0. So , You will get error as below :

If you run in Powershell 7 , then the issue is that the command you are using to get resource group names by using select-object returns output with a CRLF endings and using that as a parameter in another command will give you below errors: