Sign the Microsoft.Windows.Sdk.Win32Docs.dll assembly

[AArnott]

We need to build it, sign it, then pack it.

[AArnott]

I've verified that the dll is now signed, and that the docs package gets a new version so that it will actually push.

[riverar]

What's the new assembly for?

[AArnott]

What new assembly? This change doesn't introduce a new assembly. It just signs an existing one.
If you're wondering what Microsoft.Windows.Sdk.Win32docs.dll is for, it just defines the schema for the apidocs.msgpack file.

[riverar]

Ah neat, thanks. Wasn't familiar with this assembly.

[timsneath]

@AArnott is it documented somewhere by any chance?

[AArnott]

@timsneath Not that I know of, but that would only be due to lack of time. This package is meant for consumption by any other projection.

[timsneath]

Is it used by another projection like C#? If there's some existing code that could act as a breadcrumb trail for me to follow, I'd appreciate anything you can offer!

[AArnott]

@timsneath, breadcrumb follows:

1. note the nuget dependency from my projection to the docs package. See also source. This package contains both the assembly that defines the schema and the msgpack docs content itself.
2. How I deserialize the docs file. ApiDetails is the type defined within the Microsoft.Windows.Sdk.Win32Docs.dll assembly. I find the file to deserialize via an msbuild property that is set here based on an msbuild item that is defined by the docs package itself.
3. How I actually produce the source doc comments in the emitted code.

[timsneath]

Thanks Andrew! I'll take a look.