Can Visual Studio remember a MD5 of my source files in order to avoid rebuilding them when the timestamp changed but not the content? -
most of time doing several distinct developments on same project and, in order have logical separation between them, use personal version control system on project (namely fossil mabye detail).
this allows me commit work in different branches in order merge them afterwards. meanwhile maintain trunk branch in commit work coworkers.
but when switch branch 1 (in order perform merge action instance) , go came from, visual studio detect timestamp modifications , rebuild files have not modified.
is there way ask visual studio consider source file has changed when hash of contents has changed?
as answer seems “no” here way of achieving like, starting bounty. still read above please.
do know of simple way have snapshot of timestamps , md5 hashes of source files, , then, every file of timestamp changed, compare md5 , rollback timestamp modification if md5 has not changed?
thank answers.
i'm afraid not possible.
the issue here not thing vs entire build system quite separate actual ide.
in order decide if , .obj
should compiled, vs compares timestamp of source file. doing suggest require .obj
file include md5 of file. goes .exe
, .dll
files. changing binary format of these files , unlikely happen such needed feature.
edit - take back, possible in theory. 1 way go write vs plugin. plugin save md5s file in output directory , before build starts update modified dates of appropriate files.
thinking further, might possible using pre-build step..?
Comments
Post a Comment