The DLLs in that screenshot are for the package which is being packed. One for each of the targeted runtimes supported. These DLLs are necessary for users to be able to use the package. Is there a different result you were expecting?

@jgonz120 the first screenshot shows the nuspec includig .winmd files, not .dll. The .dll assemblies will only work (maybe?) for .NET UWP apps, but .winmd will work for both .NET and also C++ UWP apps.

@zivkan oh, I assumed because the other packages include the DLLs without specifying them in the nuspec they were meant to show up. Now that I followed the tutorial, I'm no longer seeing the DLLs:

So we should just update the doc?

It was originally reported in the docs repo, but because the docs team were planning to turn off issues in the docs repo (which they have done since then), they instructed people to re-create the issues here (and the docs person, I think his account name is something like mikejo5000) created a bunch here.

We don't have a new issue template for docs, hence why all the docs issues that were recreated in home were created with the bug template.

So, can anyone direct me to the right place to file documentation issue? I have a bunch of others I want to raise. I don't want to use the feedback link, because I want to track the updates. And I think the feedback just get mostly ignored anyways.

All the docs pages on learn.microsoft.com have feedback buttons at the top and bottom of the page. However, I'm confident it's not public, so you won't' be able to track them.

All the docs pages on learn.microsoft.com have feedback buttons at the top and bottom of the page. However, I'm confident it's not public, so you won't' be able to track them.

That does not answer my question tho. I want to know if this is the correct place to file documentation issues.