Note: This question is similar to How to prevent the copy of XML documentation files in a release mode build?, but it’s not the same and the answers there don’t apply. Read on to find out why. (Please ask in the comments or in chat if you disagree, I’ll be glad to elaborate).
I have a library project (myLibrary) and an ASP.NET web application project referencing this library (both are in the same solution). "Generate XML documentation file" is checked for the library project, because I want to have those nice IntelliSense features while developing.
When I publish the web application (Context Menu on the project/Publish…), it copies only the files required for running the application (no source code, etc.) to some publish directory. That’s good. Unfortunately, it also copies the XML documentation file of the library. Since I consider our library’s documentation to be a trade secret, I wouldn’t want it to end up on a customer’s server. Thus, we have to remember to manually remove this file from the publish directory before deploying it.
Is there a way to prevent Visual Studio from copying this file when publishing the ASP.NET project, but still retain the benefit of XML documentation IntelliSense when developing?
Assuming you’re using distinct configurations for development and release (and whatever else), unchecking ‘XML documentation file’/turning off generation for a specific configuration would prevent it being deployed when not needed. Another option would be a post-build action to delete the file/s.
The former of those two options seeming more elegant.