# Summary of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Try formulating it in user story style (if applicable): 'As a user I want X so that Y.' with X being the being the action and Y being the value of the action. --> This is basically the C# version of #84 We have a `dotnet new psmodule` in the [PowerShellStandard repo](https://github.com/PowerShell/PowerShellStandard/tree/master/src/dotnetTemplate) We should have a template for Secret Management extensions. This will help a ton with adoption because we can bootstrap the user. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. Consider providing an example PowerShell experience with expected result. --> * A `dotnet new` template with the files listed in the `C# vault extension module` section of @PaulHigin's blog post: https://devblogs.microsoft.com/powershell/secrets-management-module-vault-extensions/ * Maybe a [CodeTour](https://github.com/vsls-contrib/codetour) if we're feeling really flashy?
Summary of the new feature/enhancement
This is basically the C# version of #84
We have a
dotnet new psmodulein the PowerShellStandard repoWe should have a template for Secret Management extensions. This will help a ton with adoption because we can bootstrap the user.
Proposed technical implementation details (optional)
A
dotnet newtemplate with the files listed in theC# vault extension modulesection of @PaulHigin's blog post:https://devblogs.microsoft.com/powershell/secrets-management-module-vault-extensions/
Maybe a CodeTour if we're feeling really flashy?