@brian
I downloaded this week’s updates for V7 and WIP for offline installation.
V7 installed as usual without a new redist.
WIP sent me back to the internet to download a new redist.
Is this the expected situation, and now that I have V7 installed with the older redist can I just overwrite with the new redist or do I need to somehow have both of them in the download directory from which I run the updates for future V7/WIP updates? In other words: will future V7 updates install with the new redist I downloaded for WIP?
Rhino WIP and Rhino 7 have different requirements and redistributables. They don’t match, and we make no promise that they’ll stay unchanged into the future. Your current practice of generating the redist folders for each and moving them to your offline box is still the best way to go.
OK. I guess the way to manage the situation would be to download each version with its appropriate redist into a separate folder and do the same on the offline box. Then when I run the install each will look in its own execution folder and find the correct redist. I’ll only need to worry about deleting or renaming the old redist to allow downloading a new one when it changes for one version or the other and I won’t need to worry about one interfering with the other.
Does that sound about right?
Up 'til now I’ve managed to get away with always downloading into the default browser download directory and transferring to a common installation directory on the offline machine.