Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong documentation in Create UWP package (C#) #13586

Closed
HO-COOH opened this issue Jun 26, 2024 · 9 comments
Closed

Wrong documentation in Create UWP package (C#) #13586

HO-COOH opened this issue Jun 26, 2024 · 9 comments
Labels
Resolution:NeedMoreInfo This issue appears to not have enough info to take action Triage:NeedsMoreInfo Type:Bug WaitingForCustomer Applied when a NuGet triage person needs more info from the OP

Comments

@HO-COOH
Copy link

HO-COOH commented Jun 26, 2024

NuGet Product Used

NuGet.exe

Product Version

N/A

Worked before?

No response

Impact

It bothers me. A fix would be nice

Repro Steps & Context

Link here

Obviously, you are not packaging any dll files in the nuspec file
image

But in the result screenshot, there are dll files out of nowhere
image

I get redirected by this

Verbose Logs

No response

@jgonz120 jgonz120 added Triage:NeedsMoreInfo WaitingForCustomer Applied when a NuGet triage person needs more info from the OP and removed Triage:Untriaged labels Jun 28, 2024
@jgonz120
Copy link

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?

@zivkan
Copy link
Member

zivkan commented Jun 28, 2024

@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.

@jgonz120
Copy link

jgonz120 commented Jul 1, 2024

@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:
image

So we should just update the doc?

@zivkan
Copy link
Member

zivkan commented Jul 1, 2024

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.

@HO-COOH
Copy link
Author

HO-COOH commented Jul 2, 2024

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.

@dotnet-policy-service dotnet-policy-service bot added WaitingForClientTeam Customer replied, needs attention from client team. Do not apply this label manually. and removed WaitingForCustomer Applied when a NuGet triage person needs more info from the OP labels Jul 2, 2024
@zivkan
Copy link
Member

zivkan commented Jul 2, 2024

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.

@dotnet-policy-service dotnet-policy-service bot added WaitingForCustomer Applied when a NuGet triage person needs more info from the OP and removed WaitingForClientTeam Customer replied, needs attention from client team. Do not apply this label manually. labels Jul 2, 2024
@HO-COOH
Copy link
Author

HO-COOH commented Jul 4, 2024

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.

@dotnet-policy-service dotnet-policy-service bot added WaitingForClientTeam Customer replied, needs attention from client team. Do not apply this label manually. and removed WaitingForCustomer Applied when a NuGet triage person needs more info from the OP labels Jul 4, 2024
@donnie-msft
Copy link
Contributor

donnie-msft commented Jul 16, 2024

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.

I had to find out myself, as this process changed in recent days. No, please do not file docs issues in the Home repo. Instead, on any docs page, use the Thumbs Down button and provide the detail in the form that appears. The feedback for docs is recorded from that point. /cc @Mikejo5000

Product issues are still to be filed here on GitHub.

@dotnet-policy-service dotnet-policy-service bot added WaitingForCustomer Applied when a NuGet triage person needs more info from the OP and removed WaitingForClientTeam Customer replied, needs attention from client team. Do not apply this label manually. labels Jul 16, 2024
Copy link
Contributor

This issue has been automatically marked as stale because we have not received a response in 14 days. It will be closed if no further activity occurs within another 14 days of this comment.

@dotnet-policy-service dotnet-policy-service bot added the Status:No recent activity No recent activity. label Jul 30, 2024
@dotnet-policy-service dotnet-policy-service bot added Resolution:NeedMoreInfo This issue appears to not have enough info to take action and removed Status:No recent activity No recent activity. labels Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution:NeedMoreInfo This issue appears to not have enough info to take action Triage:NeedsMoreInfo Type:Bug WaitingForCustomer Applied when a NuGet triage person needs more info from the OP
Projects
None yet
Development

No branches or pull requests

4 participants