Microsoft.Common.tasks & Microsoft.Common.overridetasks

[ArsenShnurkov]

Both files are physically present in the repository:
https://github.com/microsoft/msbuild/blob/v16.6.0.22303/src/Tasks/Microsoft.Common.tasks
https://github.com/microsoft/msbuild/blob/v16.6.0.22303/src/Tasks/Microsoft.Common.overridetasks
Why this was necessary?
Why not to put all their content into the first file?

I am asking, because I want to redefine one task, and I am unable to deploy mine .overridetasks file, because one is already deployed (and mine file will overwrite the existing one, which is not good).

[rainersigwald]

That's a good question. I don't think the .overridetasks file is necessary, but I don't understand why it exists at all.

The original commit notes were (10/14/2008 7:54 AM)

Changeset 598865: Override tasks are required to allow msbuild 4.0 to target framework version 3.5 and lower when the toolset being used is 3.5 or lower. The reason is, when targeting .net 3.5 or lower we need to use out of process tasks. The .net 3.5 and 2.0 generate resoruce and resolve com reference tasks do in process work. We have updated the 4.0 tasks to do out of process work. The problem was, we need to be able to tell the 3.5 and 2.0 toolsets to use the 4.0 task rather than that tasks which shipped.

I'm not sure I buy that logic.

For the time being, can you just add to the .override tasks file?

[ArsenShnurkov]

can you just add to the .override tasks file?

I am using Gentoo Linux, and it is inconvenient to modify files during package installation (and modify back during deinstallation). The best design here is to have the folder for configuration files and define the load order for them. Files should be loaded in that order and next files should redefine directives form previously loaded files.
Specifically, I want to redefine ResolveAssemblyReference task to take {PkgConfig} into account - gentoo/dotnet#379

[Nirmal4G]

Related to #5190