Justin Grote

I mean there's no reason it can't be created as a vault extension, I don't think there's anything specifically in this repository that would need to be required. I'm not...

@markm77 ah I see what you are saying, yeah that would have to be owned by that team, and having them in secrets rather than the plaintext secrets.json would be...

Thanks Tyler, I figured that was pretty much the story, my current plan was to do a dotnet build against the powershell library and get an inventory of assemblies, then...

@TylerLeonhardt I made a pretty effective tool for this! It basically builds an empty dotnet project against the powershell standard with packagereferences to the required nuget packages, then copies over...

I would say this is still something that PowershellStandard should cover, as teams such as PSGet do not appear to be leveraging it and still using manual methods to pare...

@a-teece Not a maintainer on this project but what I can say is I continue to use the 5.1.0 just fine. More and more you're going to run into problems...

@a-teece I can say in my experience you can depend against PowershellStandard.Library 7-preview1 fine and mark "PrivateAssets" as true and it will "exclude" most redundancies for a .net6 or .net5...

@SteveL-MSFT @JamesWTruher I think @a-teece has a reasonable ask, seems like the README should be updated to: 1. If you need to make a module that is 5.1+ compatible, reference...

There are two vault providers that already provide this functionality: https://www.powershellgallery.com/packages/SecretManagement.JustinGrote.CredMan/1.0.0 https://www.powershellgallery.com/packages/SecretManagement.DpapiNG/0.3.0 The second one is particular interesting because you can use DpapiNG and encrypt secrets that can be decrypted...

NOTE: I am not an MS team member, just a community member @ohadschn I understand your concerns and your want, but the PS team is limited in size and effort,...