Menu
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?
816
- "Copy always" means "make sure I always have the most up to date version." - Because the build process may modify the file, the build process must be run to make sure you have the most up to date version of that file. As an alternative, "Copy if newer" won't force a rebuild.
You can copy only newer or modified files by skipping identical files. This feature will make the copy process much quicker. It is useful if you are backing up your files to the same destination.
Why not just copy the file built previously? Because the file built previously may have been modified (or created) by the build. The build process interprets "Copy Always" to mean "copy the file once the build has completed, so it's the most recent version."
12 common risks of printing/scanning and copying Risk 1: Paper gets left on the printer or copier tray Risk 2: Everyone in the office, including visitors can copy or scan to email/folder or fax Risk 3: Anyone, including visitors, can access the scan to/print from USB function on MFDs
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.
166
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
