feat: Create a Build task for DsCOM

[carstencodes]

Preface

DsCom is cool, but it lacks support for build within msbuild.

Details

This pull requests adds a nuget package that cares about exporting the Assembly to a type library automatically.
Do to a limitation in msbuild, it is not properly possible to load dependent assemblies in build task.
As suggested by Nate McMaster the task is now bundled in two ways (cf. src\dscom.build\DsComPackaging.targets ):

• The build task comes as a native MsBuild Task. It bundles dSPACE.Runtime.InteropServices and loads the file automatically.
• The targets for .NET Standard 2.0 and x86 call the DsCom Exe. The Exe file is bundled within the package using a SingleExecutable (i.e. with IL Merged InteropServices-Assembly) in both architectures - 32 and 64 bit.

Features

• Call TypeLibrary Converter within an MsBuild task
• Add Verbose and diagnostic logging
• Check, if desired TLB exists after the build
  • Provide a warning, if the type library file is missing after the build
  • Add a code to the warning to provide the user setting WarningsAsError (DSCOM001)
• Allow override for the build task to use Tools
• Automatically determine name and path of the targeted type library from the targeted assembly
• Add Included Reference Files to Assembly path

Quality Assurance

• Unit tests are written. They are now marked explicitly as a single Pull Request Action.
• The x86 example serves as Acceptance test
• The OutProc example serves as Acceptance test
• The acceptance tests are part of a pull request

Continuous Integraion

• The Code Style check has been moved to a new location
• The build task package is packed during the build
• The build task package is pushed to nuget.org during the release

Documentation

• A ReadMe.md is provided by @carstencodes
• The description for the NuGet Package is set to the readme.md
• Add architecture decision records
• Add a documentation for the implementation

Known Limitations

• Resulting package is not marked as .NET Standard 2.0 compliant. Clients must suppress NU1701 for this package, if the Assembly targets .NET Standard 2.0 (cf. OutProc Example). A bug must be filed. @carstencodes Severity: Major
• In some cases the build does not provide a type library. (cf. Outproc Example). A bug must be filed. @carstencodes Severity Major

Contained fixes

• RegistryHelper of OutProc Example contained a cast from nullable to non-nullable (Compiler Warning)

Review

• @marklechtermann (Mandatory)
• @matthiasnissen (Mandatory)
• @SOsterbrink (Optional)

[marklechtermann]

Hello Carsten,

as discussed the following change requests:

• docs should be removed
• docs/dscom.build/ReadMe.md should be moved to src/dscom.build/docs/README.md
• the content of src/dscom.build/ReadMe.md should be moved to README.md

Thx, Great work!

[carstencodes]

Hello Carsten,

as discussed the following change requests:

• docs should be removed
• docs/dscom.build/ReadMe.md should be moved to src/dscom.build/docs/README.md
• the content of src/dscom.build/ReadMe.md should be moved to README.md

Thx, Great work!

I appreciate your feedback. I have submitted e36ea67 and 04afc4b containing the requested changes.

[carstencodes]

Mentioned commits have changed. As requested by @marklechtermann I have rebased the branch onto the latest upstream main branch. Content still stays the same.

The recent three commits should contain the requested changes.

[SOsterbrink]

Looks good. I added a few questions to better understand your work.
Thanks for your work and your attention to detail.