Quite a lot of people download the source zip and then start asking why it won't compile and the stock answer is that it is for reference. Now the code is on Codeplex you can download the code as a zip without the need to install Git and go through that learning curve.
Instead of the build process generating the zip could it interface to Codeplex and get the source zip from there? Alternatively should the release not include the source but document how to go to Codeplex and download it.
Originally opened by neilsl
The text was updated successfully, but these errors were encountered:
It's an interesting thought. However, the source code needs to match the .pdbs so you'd actually need to get the code from Codeplex that matched a git tag exactly in order to debug successfully. I think we need the .zip files still for that case.
The source code as a .zip file from Codeplex might work for official releases since you can get the "latest zip file" per branch. However, the branches need to remain frozen after release for that to work (which is typically how it works but no exceptions would be allowed). But it would clean up the final releases.
Replace pdb and src zips with one "dev"/"debug" zip that includes both. Rationale: The pdbs and sources need to be in lock-step anyway and it prevents people from thinking that the src zip is buildable.
Originally posted by barnson Area set to installer
The build machine has the exact sources used to generate the build, including pdbs, so I'm not sure what benefit there would be of also downloading it from Codeplex. Also, Codeplex doesn't seem to have a predictable URL pattern to point to a particular commit for downloading. We could point to the browse view of a particular commit and say "click Download" but not automate it.
The pdbs as-shipped work for debugging release code, as well as possible given optimizations. If that's not the case with v3.8, it's a bug.