Deploy all files in a website or just the ones required to run it?

Just wondering is there any drawbacks to publishing a ASP .开发者_高级运维NET web application by copying all the files in it? (That means all the .cs, .csproj files will be included in the published folder)

So far I can think that the published folder's total size may become a little bigger (but that a negligible issue for me).

---

I would also have some security concerns here as you are posting files to a (production?) server that have no business being there. If one was to compromise your server or find a way to get those files from IIS, they could in theory gain access to all of the .cs files used to create your dll's for your web app. Space is another concern as well.

---

When publishing the codebehind-files malicious users could access your code, and find an opening for attacks.

---

I do only the files needed to run the site, but more from an intellectual property standpoint. The business logic and data access stuff is mine. My client gets what they need to run their site and go about their business. They didn't pay me to know how I accomplish those things. I want them to have to come back to me and need me to make a change, not pass it off to someone else who might benefit from my design (although, that's doubtful, I've seen my code).

---

What, apart from making the publishing process more complex than need be?