Comments (9)
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?
from home.
@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.
from home.
@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?
from home.
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.
from home.
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.
from home.
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.
from home.
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.
from home.
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.
from home.
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.
from home.
Related Issues (20)
- ProjectReference causing PM UI to error with "Value cannot be null. Parameter name: frameworkIdentifier"
- Navigation telemetry for Owner Profile URLs in PM UI
- Document source-only packages HOT 1
- NuGet discovers credentials providers installed using .NET tools HOT 1
- NuGet executes credentials providers installed using .NET tools
- [Epic] Support for credential providers deployed via .NET tools HOT 1
- Add msbuild extension point after Directory.Packages.props is imported HOT 1
- Collect telemetry for HTTPS sources with HTTP resources
- An item with the same key has already been added restoring in Visual Studio when two projects have the same name HOT 1
- Version conflict with Nuget.Frameworks.dll in .Net SDK 8.0.401
- Wrong version in API V3
- NU1503 Warning documentation is lacking information
- Navigation telemetry for hyperlinks: License, ReportAbuse, Readme, ProjectUrl
- NuGet Error: Unable to parse version value '2.0.0-beta.3' from 'packages.config HOT 2
- NuGet client (via dotnet SDK) incorrectly warns about vulnerable NuGet packages hoisted by the shared runtime HOT 4
- Report real transitive reference versions in `dotnet nuget why`, not final resolved versions
- Allow packages to suppress NuGetAudit warnings from their transitive dependencies HOT 2
- [Bug Bash] Only one error NU1004 displays in Error List window with the solution contains multiple non-SDK projects after restoring with enabled “RestoreLockedMode”
- Test the top X packages w/ sbom-tool support HOT 1
- Package Manger output and VS status bar restore updates are not available on solution load
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from home.