[Bug] Hosting build under IIS reveals a lack of flexibility

[mabakay]

Generating "Build" copies all files in bulk with the same structure and names as the original folder. When build Unity project to standalone target it creates such files like "...\Mono\etc\mono\2.0\web.config" which is IIS configuration file. And when trying to download this (and some other files) client get response code of 500. In turn patches are zipped in one file with popular ".zip" extensions which does not creates any problems when downloading them.

My suggestion is to use the same mechanism (or similar) when creating "builds". Files can still be copied separately - which ensures trouble-free downloading each individual - but on server side files can be zipped or at least extensions can be suffixed witch something like ".zip" and just removed/decompressed on client side.

[emanzione]

Yeah, I agree with you that this would be great to have.
Unfortunately, this is the result of legacy code and changing how it works right now would mean breaking the updating system for many games.
I need to think about how to offer this feature by maintaining retro-compatibility. Possibly I'm gonna tackle this after the 2.6.0 release, hopefully.

For sure I planned it for the Enterprise version, so if this cannot make it into the 2.x version of PATCH, it will be surely shipped with 3.x.

[mabakay]

It could be opt-in feature in 2.x and opt-out (default) in 3.x. Or just feature to enable regardless of version.