@thiagolimadesousa4012
Thanks so much! Your tutorial is the best. It's super clear and to the point. Nice work!
@ManontheOutside
Thanks Mark, great tutorial, very clearly explained!
@henrydeveloper2388
Very good video, thanks Mark
@Smruti-sx1gq
Thank you for such a informative video.
@juliangzr4998
Thank you very much!! it was very useful for me
@timroberts_usa
thank you for the great work you put in to show the process and details. Have you put together the command lines so it can be done in vscode?? Would be great.
@zephaneas
I just came across this. Very nice! I learned something. But I have a question... I would need to give my team the token, correct?
@alisriti3002
love it.
@ivandrofly
good stuff, thanks
@CarrigansGuitarClub
Great video - is anybody able to consume your package (when they have your username & key)?
@phillipboejensen8957
Do you explain how to consume these authenticated packages in an automated way? I have a authenticated NuGet package that i would like to be available to my team when they launch our code from our devcontainers. Is there a smart way to do this?
@mk553
How do you get past all the 406 'unacceptable' errors when pushing the packages to the source?
@holger_p
This was valuable, although the content was more "how to create and consume nuget packages", the "private" and "team" parts, as promised in the title got completly lost. I got really no idea, why not just anybody could consume your uploaded package, you didn't pass any credentials on install package (cause you are already logged in to github) and you didn't assign any rights to any other person (from the team), nor set anything to make it non-public. Getting access to something, is the rather easy part; Ensuring somebody else or the public has no access, is hard to verify.
@emreduman225
Great content! Can you make another video about this content but using .Net 8, and in this video can you specify the title with ".net 6".
@mbv401920150