Description:
The Sandbox contains broken "Add String" buttons when viewing the following object types:

• DriverObject under "LinkedAgainst"
• FirewallObject under "LocalAddresses"
• FirewallObject under "LocalPorts"
• FirewallObject under "RemoteAddresses"
• FirewallObject under "RemotePorts"
• RegistryObject under "Permissions"
• RegistryObject under "SubKeys"

Expected behavior:
The "Add String" buttons should add strings to a list displayed as a dropdown

To Reproduce:
Steps to reproduce the behavior:

1. Run ASA, open GUI
2. Click Sandbox page
3. Select any of the above mentioned types, e.g. DriverObject
4. Create the object
5. Click 'View' tab to view the object, expand its contents
6. Find some broken "Add String" buttons

Configuration:

• ASA Application Version: v2.3.146-beta
• OAT Application Version: 718b12b

Using the code from operations tests

For reporting purposes it is valuable to identify which of N number of patterns in a Clause represented in the Data list were actually responsible for the capture. There doesn't appear to be a way to determine that today. For example:

        var trueRegexObject = "zcash";

        var regexRule = new Rule("Regex Rule")
        {
            Clauses = new List<Clause>()
            {
                new Clause(Operation.Regex)
                {
                    Data = new List<string>()
                    {
                        "cardano|ethereum|cryptocurrency",
                        "p2pool|miner|ripple|nxt|tether|ether|btc|zcash|monero|merkleroot|xmr|eth"
                    }
                }
            }
        };

        var regexAnalyzer = new Analyzer();
        var ruleList = new List<Rule>() { regexRule };
        IEnumerable<RuleCapture> captures = regexAnalyzer.GetCaptures(ruleList, trueRegexObject);

Description:
In the Sandbox, objects containing flag enum members do not display corresponding enum content when viewed. Only the label is displayed.
E.g. see FirewallObject flag enum member 'Profiles'

Expected behavior:
Objects in 'View' mode should display all possible enum flag values as checkboxes, defaulting to unchecked.

To Reproduce:
Steps to reproduce the behavior:

1. Run ASA, open GUI
2. Click Sandbox page
3. Select type that contains flag enum input, e.g. FirewallObject
4. Create the object
5. Click 'View' tab to view the object, expand its contents
6. See labels where flag enum inputs are not being populated, for example 'Profiles' label when viewing FirewallObject

Configuration:

• ASA Application Version: v2.3.146-beta
• OAT Application Version: 718b12b

Follow on from #79 where we added support for Lists of any type of object.

Proposed Change

Add a string field Lambda to clause that when not null contains C# code to execute in lieu of writing a delegate ahead of time.

New Behavior:

• When Lambda is set Lambda is used.
• Otherwise, the operation delegates set in the analyzer are checked as usual against the CustomOperation field.
• CustomOperation is still required to label the operation.
• During validate rules only attempt to compile the lambda
• During validate rules ensure there is a defined operator in the dictionary as usual or a lambda.

See: https://www.strathweb.com/2018/01/easy-way-to-create-a-c-lambda-expression-from-a-string-with-roslyn/

Description:
The Sandbox contains broken "Add KVP" buttons when viewing the following object types:

• DriverObject under "Properties"
• FileSystemObject under "Permissions"
• RegistryObject under "Values"
• UserAccountObject under "Properties"
• GroupAccountObject under "Properties"

Expected behavior:
The "Add KVP" buttons should add KVP to a list displayed as a dropdown

To Reproduce:
Steps to reproduce the behavior:

1. Run ASA, open GUI
2. Click Sandbox page
3. Select any of the above mentioned types, e.g. DriverObject
4. Create the object
5. Click 'View' tab to view the object, expand its contents
6. Find some broken "Add KVP" buttons

Configuration:

• ASA Application Version: v2.3.146-beta
• OAT Application Version: 718b12b

Desired Goal

When calling ctors for objects in Blazor we should include all the assemblies that the user has loaded so that Types that require components from another Assembly can be created.

Blocked by dotnet/roslyn#39501

You may get a lot of warnings when loading stuff in the sandbox which pushes the interactive content way down the page. The messages should scroll or collapse or some other hiding method by default to reduce the amoutn of page they take up.

Create a blazor sandbox to play with the demo objects and rules and to create your own objects and rules based on assemblies you provide.

Assembly version is being reported as 1.1.0.0. Build pipeline issue?

Currently we only check object Properties and ignore Object fields.

We should also allow running rules against Object fields.

Description:
In the Sandbox, constructor parameters with enum types are displayed as text input fields in 'Create' mode.

Expected behavior:
Enums should be displayed as dropdown selection boxes that contain enum values in 'Create' mode.

To Reproduce:
Steps to reproduce the behavior:

1. Run ASA, open GUI
2. Click Sandbox page
3. Select type to create that contains enum input, e.g. ComObject or CryptographicKeyObject
4. See text input fields where dropdown is expected.
   For example with ComObject, see constructor 'View' field
   For example with CryptographicKeyObject, see constructor 'tpmAlgId' field.

Configuration:

• ASA Application Version: v2.3.146-beta
• OAT Application Version: 718b12b

Line 13 of ObjectInput.razor

Follow up from #81. Dictionaries keyed with other objects may be useful. For example, ASA has a dictionary keyed with a tuple of an Enum and a uint.

Also should improve the handling of what can be contained in the value of a dictionary as currently it uses a scaffold for the second parameter even if it doesn't need one

i.e. for strings etc. Depends on .NET 6.

dotnet/runtime#56322 (comment)

This requires a rewrite of the EnumerateRuleIssues API. Likely to

public (bool Applies, List<Violation>) EnumerateRuleIssues.

See: https://github.com/microsoft/OAT/pull/65/checks?check_run_id=3165722865

For example, if you try to change the value of a field of a ValueTuple it will successfully recursively get the valuetuple and then successfully set the value of the field. But because it was passed by value it only changes the value in the local copy, not the original that was passed in.

Remove the dependency on Newtonsoft.

Show the full list of assemblies that the user has loaded in the Sandbox and Author pages

Probably as a Select dropdown.

https://bunit.dev/

Currently when you try to build release you get a linker error about Blazor.FileReader. We need to resolve this so we can publish a trimmed Release version of OAT Wasm.

  Fatal error in Mono IL Linker
/Users/gabe/.nuget/packages/microsoft.aspnetcore.components.webassembly.build/3.2.1/targets/Blazor.MonoRuntime.targets(326,5): error : Unhandled exception. Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Blazor.FileReader, Version=0.11.19128.0, Culture=neutral, PublicKeyToken=null' [/Users/gabe/Documents/GitHub/OAT/OAT.Blazor/OAT.Blazor.csproj]
   ---> Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Blazor.FileReader, Version=0.11.19128.0, Culture=neutral, PublicKeyToken=null'
     at Mono.Cecil.BaseAssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters)
     at Mono.Linker.AssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters)
     at Mono.Linker.LinkContext.Resolve(IMetadataScope scope)
     at Mono.Linker.LinkContext.Resolve(IMetadataScope scope)
     at Mono.Linker.LinkContext.ResolveReferences(AssemblyDefinition assembly)
     at Mono.Linker.Steps.LoadReferencesStep.ProcessReferences(AssemblyDefinition assembly)
     at Mono.Linker.Steps.LoadReferencesStep.ProcessAssembly(AssemblyDefinition assembly)
     at Mono.Linker.Steps.BaseStep.Process(LinkContext context)
     at Mono.Linker.Pipeline.ProcessStep(LinkContext context, IStep step)
     at Mono.Linker.Pipeline.Process(LinkContext context)
     at Mono.Linker.Driver.Run(ILogger customLogger)
     at Mono.Linker.Driver.Execute(String[] args, ILogger customLogger)
     at Mono.Linker.Driver.Main(String[] args)
/Users/gabe/.nuget/packages/microsoft.aspnetcore.components.webassembly.build/3.2.1/targets/Blazor.MonoRuntime.targets(326,5): error : ILLink failed with exit code 134. [/Users/gabe/Documents/GitHub/OAT/OAT.Blazor/OAT.Blazor.csproj]