Set copyright and package license

[tmat]

Prepares repo for change dotnet/arcade#2003 by setting Copyright and PackageLicenseExpression properties. These values will be required to be set by each repository once dotnet/arcade#2003 is merged.

In order to not break the current builds this change sets the properties conditionally. This condition can be removed once all repos switch to Arcade that has dotnet/arcade#2003.

@markwilkie

[safern]

LGTM, but I know @joperezr imported the props at the end for a specific reason, plus set the MicrosoftCompiler property to false for something specific that I don't remember.

[tmat]

UsingToolMicrosoftNetCompilers is false by default. It used to be different, so now it's not necessary to override it anymore.

The recommendation is to import Sdk.props first:

The Sdk.props file sets various properties and item groups to default values. It is recommended to perform any customizations after importing the SDK.

BTW, setting <Language>C#</Language> seems unnecessary. The language is determined from the project extension (e.g. .csproj).

[tmat]

OT: All the logic in /build.proj seems unnecessary as well. This is replicating/circumventing similar Arcade build logic. Why not have a solution that contains all the projects and build that solution?

[safern]

BTW, setting <Language>C#</Language> seems unnecessary. The language is determined from the project extension (e.g. .csproj).

Agreed.

OT: All the logic in /build.proj seems unnecessary as well. This is replicating/circumventing similar Arcade build logic. Why not have a solution that contains all the projects and build that solution?

I think @joperezr wanted control over what targets are run on which projects and he's concerned that this repo is potentially going to grow to a handful amount of projects as they add bindings and drivers, potentially something like corefx, over 500 projects, from last time I spoke to him, that where the insights he told me.

[tmat]

@safern @joperezr I'd rather avoid replicating CoreFX build structure unless absolutely necessary and instead I'd strongly suggest to follow what all other repos are doing. We have 180 projects in Roslyn repo and there haven't been any issues. If any issues arise we need to address them in the product and/or in Arcade SDK, not in each repo separately.