Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In order to avoid rebuilding the libraries that have not been touched I’m changing Copy to Output Directory for some files from Copy always to Copy if newer in some c# projects.
The files whose setting is changed have their Build Action set to one of Content, Embedded Resource, or Resource.
What are the risks accompanied with this?
Besides this probably being obsolete (e.g. due to resources being embedded), the only risk I could think of right now would be the fact that you could use outdated files in case some program changes something without updating the file’s timestamp (or modifying this timestamp). For example, you might do some local changes to a file, then revert its contents using some kind of file versioning system (like SVN or HG). It’s then possible that Visual Studio won’t notice the reverted file and it might not copy it.