Consider loading task assemblies using Assembly.Load(byte[])

A common problem is MSBuild node processes locking a task assembly file on disk and lingering, thus preventing the deletion or update of the file.

Consider reading the raw bytes from disk and loading using that, to avoid holding the .dll locked. Need to investigate whether there will be performance or other implications.

https://source.dot.net/#System.Private.CoreLib/Assembly.cs,b2d43e31d338b43c

To me the locked task .dll happens often enough that it would be warranted.

Start by tracing where MSBuild loads task assemblies, then compare that behavior with the Assembly.Load(byte[]) example at the linked System.Private.CoreLib Assembly.cs source. Investigate file-locking, performance, and other loading implications; done requires a documented decision supported by relevant tests or measurements.

Written by the indexing model from the issue text.