Generate .nupkg files that contain aspnetcore-runtime MSI for insertion into Visual Studio

[jkotalik]

Part of #11071

Packages will be put in the NonShipping folder and uploaded to the blob store.

@johnbeisner what do we need to do to verify this E2E?

[dougbu]

Looks good but please wait to hear back from @johnbeisner before merging

[johnbeisner]

@jkotalik
You should go to the VS feed and download/inspect at the existing Asp.NET NuPkgs for VS:
https://devdiv.visualstudio.com/DevDiv/_packaging?_a=feed&feed=VS

If you filter on "VS.Redist.Common.AspNet" you will see your team's VS NuPkgs - I feel we should stay with these naming/ID/versioning conventions at least thru the first insertion of 3.0 SDK into VS.

[johnbeisner]

@jkotalik
"what do we need to do to verify this E2E?"

1. produce an official Asp.NET build with the NuPkgs
2. upload the four 3.0 NuPkgs to the VS feed
3. Modify the current VS insertion PR to consume these new Asp.NET NuPkgs
   https://devdiv.visualstudio.com/DevDiv/_git/VS/pullrequest/186888

I can handle steps 2 & 3; eventually we will need to automate step 2.

[jkotalik]

Need to figure out how to ignore signing this package.

[johnbeisner]

@jkotalik
@joeloff
Pretty sure the MSIs need to be signed.

[joeloff]

The nupkg is just a delivery mechanism for getting external binaries into the VS build. As long as the MSIs are signed, we're good. The nupkg signature doesn't matter. It can either be signed or unsigned.

[jkotalik]

Chatted with @joeloff offline. The SignTool only signs nuget packages in the Build Windows Installers (not msis). Msis are signed in a separate step within the wixprojs themselves. This is the first time we are including a msi within a nuget package, so we should ignore trying to sign it. Also, we shouldn't attempt to sign it too as then we could have multiple msis with the same binaries with different signatures.

I'll verify that the contents are in fact signed. Unfortunately, this either would mean I need to make an internal PR or push and verify after I pushed.

[johnbeisner]

@jkotalik
I do not see the NuPkgs at blob storage - could I be looking at the wrong versions?

[jkotalik]

I see it being uploaded. It should be on the aspnet-aspnetcore feed. Example build version number: VS.Redist.Common.AspNetCore.SharedFramework.x64.3.0.3.0.0-preview7.19351.4.nupkg and internal build.
https://dev.azure.com/dnceng/internal/_build/results?buildId=245648&view=results