I took a look at the code, and to the topics here.
I’ve seens a lot about refactoring / supporting new features. That is nice. But, nothing to cleanup the current code.
So, this is a starting point for the cleanup which, in my opinion, should be done before opensourcing the code.
RuntimeLibrairies / ExternalReferences : are references to specifics Windows Folder. The content of this folder are simply dll, where we are, today, unable to say clearly : “Which version of is used ?”. There should be a cleanup to move this part to nuget packages usage.
GO Framework should be packable, to do that, in my mind, the projects should be set up to the new csproj format.
New csproj style are much clearer, and reduce the amount of specific data. (Removing ItemGroup with the Compile of each file, for example)
Coding style / Code uniformization : While open sourcing, there will have common questions about the style to apply to the code. Should you use spaces or tabs ? 2 spaces length ? 4 spaces length ?
How to ensure that everyone will use the same syntax ? Quite easy.
.editorconfigfile is here to do this.
Removing the dead code. Code inside Deprecated Code folder / Old / commented should not be in the current version. That the main purpose of the versionning system. If you need it at some point, you will be able to retrieve the code. Removing dead code will make potential evolution easier.
C# syntax uniformization. ie: String interpolation are not used everywhere.
Remove sensitive informations. In docker repository, I saw a password.
Adding README files. After a few years away from GO platform, it’s hard a bit difficult to know what is the purpose of each repository. Having a simple description might help contributors to know if this repository might interest them, or not.
Cleaning up the current Custom Code should be an entry point to apply this to the Generated Code.