dotnet/roslyn

Consider having CopyRefAssembly inherit from Copy

Open

#19.103 geöffnet am 28. Apr. 2017

Auf GitHub ansehen
 (3 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)C# (4.257 Forks)batch import
Area-CompilersBughelp wanted

Repository-Metriken

Stars
 (20.414 Stars)
PR-Merge-Metriken
 (Durchschn. Merge 5T 21h) (286 gemergte PRs in 30 T)

Beschreibung

The new CopyRefAssembly task has logic to determine whether a reference assembly is logically identical by comparing MVIDs of the source and destination files. If the MVIDs do not match, it copies the source assembly to the destination path.

As currently implemented, this copy doesn't have all of the bells and whistles of the Copy task, which supports retries and special-cases a number of scenarios.

CopyRefAssembly could inherit from Copy, override Execute(), do its up-to-date checks, and then after deciding to copy, forward to base.Execute() to get all of the additional magic.

This came up when discussing https://github.com/Microsoft/msbuild/issues/1986 with @jeffkl.

@jcouv -- something to think about. Doesn't block the initial implementation, since no MSBuild change would be required to pick this up.

Contributor Guide