Nov 29 2019 07:42 AM
As far as I know it's a bad idea. I've looked around but can't find specific technical reasons why it's bad to do so, can anyone advise?
Nov 29 2019 12:22 PM - edited Nov 29 2019 12:23 PM
SolutionNov 29 2019 07:12 PM
Dec 02 2019 12:02 PM
@baronnenateWhen you store a file in a library and click the file, SharePoint will attempt to launch/run the file. In the case of regular documents, that's not a problem. But if your file is an executable or html, etc. and SharePoint attempts to launch/run the file it can create problems. I locked up my entire machine once with some .exe and had to pull the plug and reboot.
If you think your users are going to remember to select the file, then click the download button to save to their hard drive before launching the exe, you have more faith in humanity than I do.
Be smart, be safe. Zip the files then upload them. Yes, it's an extra step to unzip them but it's better than the alternative.
Dec 02 2019 12:09 PM
Dec 03 2019 12:55 AM
the use case here is quite simple really, it's the storing of our product binaries/installers so we can share them with select customers (privately) without storing them somewhere public like S3 or Azure Blobthingy
Dec 04 2019 05:37 AM
@baronnenateI would zip them and then post them as desired.
Nov 29 2019 12:22 PM - edited Nov 29 2019 12:23 PM
Solution