AIt doesn't seem like something that'd need to be done asynchronously
Myes
Mis for forms
AEven more of a reason to not do it asynchronously, then
Mwhy
Mthen i get stuck on form app while hashing
Mand set as no responding
AAh, I see what you mean
Myes
M
AAnd what's the error?
MSystem.Security.Cryptography on framework doenst have thath funcion
M:D
ASo there's only a synchronous version of this method, then
Mi could downooad the package thath uses net for thath
AIdk, try
Task.Run()Just don't do what they did in the docs, the
.Wait()awaitand i can get the result?
AYou should be able to, yes
MAngius#1586
REPL Result: Success
Result: int
Compile: 600.086ms | Execution: 85.131ms | React with ❌ to remove this embed.
AAs demonstrated
Mso
Mbyte[] UnpatchedFileHash = await Task.Run(() => DigestAlgorithm.ComputeHash(FileBufferStream));
Minteresting
Msometimes i am very dumb
AIt is synchronous tho
Mamm
Mwhat
Awhat does computehash return?
Jit is, but they're using Task.Run to offload the work from the UI thread
Jso it doesn't block the UI
MDon't use Task.Run if the hash function runs for more than like 100 ms
MIt isn't designed for long-running operations
CPutting synchronous code in an async fashion does not make it run asynchronously
CIf DigestAlgorithm.ComputeHash is synchronous, running it as a task will be synchronous.
CThat’s not how it works
CTasks are ran on the main thread in a thread pool. While the synchronous code in an async function is running, execution on the main thread is blocked.
CAsync only helps when there is actual async functions within a Task
Jawait Task.Run(() => sync code here)yes, the work being done is sync, not async, but the important thing is the calling thread (the UI thread in this case) is not blocked
Jthat's what I meant by "offload from the UI thread"
JI'm also not sure what you mean by "Tasks are ran on the main thread in a thread pool"
the thread pool doesn't have a "main thread"
the thread pool doesn't have a "main thread"
Jafaik
Aah yeah you're right
Athat thought slipped my mind
CI never realized Task.Run was fundamentally different to awaiting a Task.
Swhy not, the thread pool automatically adjusts
Sitll create a new thread
CWhen you await a task normally, it’s ran on the UI thread, or whatever synchronization context you’re calling from