hello people,
i just recently made up a C# program for "DUPLICATE FILE REMOVER" (just 4 fun)
but my fun was crushed when this came up
please tell me what the problem is...
also i can post in the source if some one want to take a look at it...
-----------------------------------------
Posted again:
-----------------------------------------
also the prg does NOT give any o/p for very small file sizes.
if my guess is correct it is due to the fact that multiple files are heavily computed MD5 hash
i think the fileinfo.length method should do but it is not implemented
i just recently made up a C# program for "DUPLICATE FILE REMOVER" (just 4 fun)
but my fun was crushed when this came up
Code:
ContextSwitchDeadlock was detected
Message: The CLR has been unable to transition from COM context 0x213c40 to COM context 0x213db0 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.please tell me what the problem is...
also i can post in the source if some one want to take a look at it...
-----------------------------------------
Posted again:
-----------------------------------------
also the prg does NOT give any o/p for very small file sizes.
if my guess is correct it is due to the fact that multiple files are heavily computed MD5 hash
i think the fileinfo.length method should do but it is not implemented