Possible issues with concurrent installations

In Squirrel.Windows there is a bug that multiple deployments running at the same time on login can overwrite each other’s files in the extraction process before Updater is called to install each. I am thinking about switching to Clowd.Squirrel but wanted to see if the same problem could occur in this program. I quick look makes me think the same issue may exist. Two programs deploying on login could overwrite each other’s files as they both write to %temp%\squirrel. See updaterPath and get_temp_file_path() Am I reading this correctly (not a C++ guy)? Or are there steps to ensure they extract to different places that I’m not quite seeing.

[caesay]

In the specific parts of code you pointed out - those are not an issue here. I will leave this issue open as I still think it’s a good idea to address the incrementing temp folder creation - there is still potential for collisions there (maybe less likely than the issue you pointed out) but it will be trivial to fix.

[bzuillsmith]

Got it. Good to know Clowd.Squirrel does things a little better. Sounds like there is still some potential for problems, but much less.

To see the behavior in Squirrel.Windows – this line and this line set the target directory for extracting files from Setup.exe and this line sets it as the base directory for the extracted files. I watched the directory as the install ran and saw the files I mentioned above placed in the directory temporarily.

Feel free to close unless you feel there are things to be addressed in Clowd.Squirrel related to this