Skip to content

Conversation

@skykingjwc
Copy link

We have a script that runs after a build which copies all our assemblies to a shared bin folder. This is where we prefer to deploy from. Unfortunately, this process resets all the dates on the files, so Kudusync think every single file is new. By comparing the file hash, and in conjunction with the MSBUILD /deterministic parameter, it is possible to compare the hashes of dll files, to determine if they have changed since the last build. I added a command line option to enable hash only mode, while leaving the existing timestamp comparison feature intact.
I also noticed that verbose logging was not working, so that was fixed as well. Also overrode the logger to copy its output to the debug console, to assist in debugging.

}
}

public static string ComputeSha256(this FileInfoBase file)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given non-security related scenario, isn't the existing Sha1 method sufficient?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants