Website source control and big setup binaries

Many times website developers need to handle the download of heavy *.exe or *.msi setup files from their website. Today this involves complex hotlinking protection and multiple binaries version开发者_如何学JAVA management.

The question is: does it worth to include these heavy binaries (in our case ~300MB) to website source control? Is there any workaround to fully test the download locally without including these file - that will never change - to Team Foundation Server source control?

if the binaries are external you have two options:

option 1: I prefer to include them in your solution.

option 2: you can create a team project called "Common Binaries" and make it a shared resource of all common binaries.