Closed redtaped closed 1 year ago
After initial research, I've narrowed down proposals to rust, go or C#. C# AOT is likely not the right solution given the limitations of not being able to invoke CLI or C files, dependent libraries may not be compatible.
The best compromise if we choose C# is to publish as a self contained application where the framework is included in the release. This satisfies AC#3. https://learn.microsoft.com/en-us/dotnet/core/deploying/#publish-self-contained.
Rust or Go would be useful because they are inherently able to ship as a self contained binary with no runtime dependencies. But limited exposure to these langauges limits their effectiveness for the current owners.
During backlog refinement, we determined that a self contained C# application is viable, it can launch processes using the Process class and we can manage the window size and location using the lower level unmanaged windows libraries
Team determined that C# with self-contained framework is the best solution for this initiative. We can revisit other options if we become blocked by this approach.
Deployment can just be a zip file for MVP that includes all required binaries and exes
No license for now
As a developer I’d like to explore the available frameworks and languages available to reach MVP milestone. An initial scaffold of the chosen language and framework should be submitted as a PR.
Acceptance Criteria