Research project of the Cluster of Excellence "Integrative Computational Design and Construction for Architecture" (IntCDC) https://www.intcdc.uni-stuttgart.de/ **Project Name**: Knowledge Representation for Multi-Disciplinary Co-Design of Buildings. https://www.intcdc.uni-stuttgart.de/research/research-projects/rp-20/
Because the current installer (online version) fetches the ZIP file from the Releases page, we need to make a new release every time we want to ship a new version. (Remember the offline version is just another zip file that we can download with the assemblies in the same folder, so the same reasoning applies to it too).
Instead, we can modify the online installer and build events to allow for more automation. For example, via build events, we can copy the compiled assemblies not only to the BHoM installation folder, but also to a central location in the GitHub repository. (we already have these build events actually -- we also copy to a Build folder in the GitHub repository). We can then publish these assemblies as part of the repository files (not a good practice, but useful and justifiable for our case). If we do so, the online installer can download the assemblies from this location instead that from the Releases page.
This would remove the need to do a Release every time we merge a PR to main. This also means we need to be even more careful about what we merge to main.
Please remember that the "offline" installer will still require that we package all the compiled assemblies in a zip file together with the offline installer script. However, this can be done on a demand basis (i.e. when and if we ever need to do this, like when in the past we collaborated with people that could not access GitHub due to governmental restrictions).
Description:
Because the current installer (online version) fetches the ZIP file from the Releases page, we need to make a new release every time we want to ship a new version. (Remember the offline version is just another zip file that we can download with the assemblies in the same folder, so the same reasoning applies to it too).
Instead, we can modify the online installer and build events to allow for more automation. For example, via build events, we can copy the compiled assemblies not only to the BHoM installation folder, but also to a central location in the GitHub repository. (we already have these build events actually -- we also copy to a
Buildfolder in the GitHub repository). We can then publish these assemblies as part of the repository files (not a good practice, but useful and justifiable for our case). If we do so, the online installer can download the assemblies from this location instead that from the Releases page.This would remove the need to do a Release every time we merge a PR to main. This also means we need to be even more careful about what we merge to main.
Please remember that the "offline" installer will still require that we package all the compiled assemblies in a zip file together with the offline installer script. However, this can be done on a demand basis (i.e. when and if we ever need to do this, like when in the past we collaborated with people that could not access GitHub due to governmental restrictions).
@DiellzaElshani @polnischfrosch