I suggest you ...

Make WebDeploy CRC check more efficient

Now when we have MSDeployUseChecksum it works great in terms of precision but slow in terms of performance. This is a problem for a larger websites because it takes up to 4, 10, ... minutes to calculate the checksums.

Here is the idea: combine time stamp checks with CRC.

Algorithm: do a time stamp check first. Then do a CRC check for all found differences.

This will improve performance for some frequent scenarios while keeping the precision.

17 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Alex shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Ingo commented  ·   ·  Flag as inappropriate

        Should be improved.
        Have a medium size project and when I use MSDeployUseChecksum it take around 20 minutes to deploy. Deploying the whole project from the scratch doesn't take much longer...

        Have tried to calculate crc of all my project files (+- 6800) and it take around 60 seconds using the nuget package Crc32C.NET.

        Either that implementation is much faster or something else is going wrong here.

      Feedback and Knowledge Base