Nuget.Org now supports .snupkg packages for portable PDBs, replacing the old symbols.nupkg format.
Additionaly, since we use myget for staging prerelease packages, it would be great if pushing to an upstream source also pushed the symbol package, if present.160 votes
We’d like to inform you regarding updated NuGet Symbol Packages .snupkgs support, which will be released next month. It’s in QA at the moment.
We’ll inform you regarding other ongoing updates soon.
Thanks for being with us!
It would be great to have an API to automate certain tasks on MyGet!35 votes
Please reach out to us and let us know which operations you would like to see in a first version of the API.
I'm hoping that a more secure ADFS experience/workflow can be created. I would like to see a situation where an administrator can restrict token-based authentication for feed consumers and the consumers can use some sort of Nuget ADFS CredentialProvider to authenticate against the feed. (Perhaps with single-use, short-lived tokens generated by the provider?) That way when an AD account is disabled there is no need to secondarily disable a myget account.3 votes
Have you tried our new MyGet Credential Provider for Visual Studio 2017 yet? http://docs.myget.org/docs/reference/credential-provider-for-visual-studio
We are working on improving that very experience, so we’re very eager to hear your feedback on this.
Please support Windows Azure Active Directory for private feeds.10 votes
Situation: TeamCity build definitions with project names that contain capital letters. There are build templates that use the project name variable to do all sorts of things, from pulling from GitHub through to publishing packages.
MyGet forces all feed names to be lower-case, which means that we can't use project name variables to push to a MyGet feed.1 vote
Ability to create "Service" users who don't have an email address and aren't linked tro an identity provider
I would like to set up user accounts for our Build Servers that publish packages and our Octopus Deploy server that needs read only access to our Package Feeds.
Currently I can't set this up as the users in question are obviously not people and don't have email addresses for them.8 votes
We are thinking of making API keys “scoped”, so that you can create an API key that, for example, can only consome and/or push to a given feed. Would that work?
- Don't see your idea?