11. A computational process for determining whether to regenerate code-behind file(s) based on fingerprint(s) of selected metadata, the process comprising the computational steps of: starting a software application build which is an attempt to build an application in a computing environment having random access memory in communication with at least one processor; identifying a binary-file-set as a system binary-file-set which has been derived by compilation or interpretation, as opposed to being a non-binary file, and then avoiding computing a current metadata-fingerprint for that system binary-file-set; proactively computing respective metadata-fingerprints for dependent binary-file-sets of the application, each binary-file-set having a respective metadata-portion and a respective distinct non-metadata-portion, each metadata-fingerprint computation based at least in part on the respective metadata-portion and independent of at least part of the respective non-metadata-portion, wherein the metadata-fingerprint computation for at least one binary-file-set is not based on any system binary-file-set current metadata-fingerprint; and computationally and proactively determining whether to regenerate a code-behind-file-set based at least in part on whether the metadata-fingerprint for the binary-file-set has changed since a previous attempt to build the application, wherein the determining step comprises checking whether a timestamp of a code-behind-file-set matches a timestamp of a user-interface-file-set of the application.
11. A computational process for determining whether to regenerate code-behind file(s) based on fingerprint(s) of selected metadata, the process comprising the computational steps of: starting a software application build which is an attempt to build an application in a computing environment having random access memory in communication with at least one processor; identifying a binary-file-set as a system binary-file-set which has been derived by compilation or interpretation, as opposed to being a non-binary file, and then avoiding computing a current metadata-fingerprint for that system binary-file-set; proactively computing respective metadata-fingerprints for dependent binary-file-sets of the application, each binary-file-set having a respective metadata-portion and a respective distinct non-metadata-portion, each metadata-fingerprint computation based at least in part on the respective metadata-portion and independent of at least part of the respective non-metadata-portion, wherein the metadata-fingerprint computation for at least one binary-file-set is not based on any system binary-file-set current metadata-fingerprint; and computationally and proactively determining whether to regenerate a code-behind-file-set based at least in part on whether the metadata-fingerprint for the binary-file-set has changed since a previous attempt to build the application, wherein the determining step comprises checking whether a timestamp of a code-behind-file-set matches a timestamp of a user-interface-file-set of the application. 13. The computational process of claim 11 , wherein the metadata-fingerprint computation for at least one binary-file-set is based on class(es) that are used when generating the code-behind-file-set corresponding to that binary-file-set, and is not based on any class that is not used when generating that code-behind-file-set.