Support launching app with file for win and linux

[schaveyt]

Status: Review Approved

Summary

Addresses #647 and remains compatible with existing behavior of passing arguments via /args commandline option.

This has been built and integration tested locally by invoking via electronize start as well as the compiled executable as described in the issue #647.

Change Summary

1. Added the new Process class and singleton, this required:
   1. Updating ElectronNET.API/Electron.cs to add access to the Process singleton
   2. Updating ElectronNET.API/ServiceCollectionExtensions.cs to register Process singleton to the DI container
   3. Updating ElectronNET.CLI/Commands/Actions/DeployEmbeddedElectronFiles.cs to deploy the new embed the new .js file
   4. Updating ElectronNET.CLI/ElectronNET.CLI.csproj to embed the new process.js file to the CLI.
   5. Creating ElectronNET.Host/api/process.ts to interact with Electron's process object from the node side
   6. Creating ElectronNET.API/Process.cs to bridge with the electron api
   7. Updating ElectronNET.Host/main.js to initialize the processApi object.
2. Updated ElectronNET.API/BridgeConnector.cs to add reusable methods to obtaining values over the Socket interface.
3. Updated ElectronNET.API/Entities/ProcessVersion.cs as corresponding type to the electron.process.versions type.

Verification Summary

I was not able to get the WebApp project running however I was able to get my target project running with the update API & CLI changes. I created a simple test method as follows:

    public async void VerifyProcessApi()
    {      
        Console.WriteLine($"VerifyProcessApi START------------");
        Console.WriteLine($"Electron.Procsss.ExecPath='{await Electron.Process.ExecPathAsync}'");
        Console.WriteLine($"Electron.Procsss.TypeAsync='{await Electron.Process.TypeAsync}'");

        var argv = await Electron.Process.ArgvAsync;
        var argvLength = argv != null ? argv.Length.ToString() : "null";
        Console.WriteLine($"Electron.Procsss.ArgvAsync.Length='{argvLength}'");
        if (argv != null)
        {
            var msg = "\n";
            for (var i = 0; i < argv.Length; i++)
            {
                msg += $"argv[{i}]='{argv[i]}'\n";
            }

            Console.WriteLine(msg);
        }

        var versions = await Electron.Process.VersionsAsync;
        Console.WriteLine($"Electron.Procsss.VersionsAsync='[Chrome={versions.Chrome}, Electron={versions.Electron}']");

        Console.WriteLine($"Electron.Procsss.DefaultAppAsync='{await Electron.Process.DefaultAppAsync}'");
        Console.WriteLine($"Electron.Procsss.IsMainFrameAsync='{await Electron.Process.IsMainFrameAsync}'");
        Console.WriteLine($"Electron.Procsss.ResourcesPathAsync='{await Electron.Process.ResourcesPathAsync}'");
        Console.WriteLine($"Electron.Procsss.UpTimeAsync='{await Electron.Process.UpTimeAsync}'");
        Console.WriteLine($"Electron.Procsss.PidAsync='{await Electron.Process.PidAsync}'");
        Console.WriteLine($"Electron.Procsss.ArchAsync='{await Electron.Process.ArchAsync}'");
        Console.WriteLine($"Electron.Procsss.PlatformAsync='{await Electron.Process.PlatformAsync}'");
        Console.WriteLine($"VerifyProcessApi END------------");
    }

The generated the following results with no issues.

Results:

[danatcofo]

Very nice. There's an open PR that converts all the singletons into interfaces that will need updating after this one as it will conflict but that isn't this PRs problem.

[danatcofo]

If these are read only values you might make the set internal for these two props.

[schaveyt]

Alternatively, i figured this would be a perfect use case for using a record type to achieve the desired read-only behavior. See my latest commit.

I have re-run all my tests and encountered no issue with this change. 👍