This message was deleted.

Given your just writing dotnet code a lot of the standard good library design for C# applies equally well to Pulumi. About the only Pulumi specific thing you'll really need to know about is Component Resources. Our devrel team might have some other resources when they get online in the US timezone.

@echoing-dinner-19531 - Thanks. A small sample would be helpful, hopefully the US folks can point me to one.

I believe there is a .NET sample in that component resources documentation. The trick with these is just to make sure you are always setting the parent on child resources, and that you are forwarding any providers provided to the component resource via custom resource options. I have done something similar to this - you'll want to publish a class library that exposes the component resources and their respective argument classes and that will be about it. I like to follow the way the various Pulumi providers define & name argument classes.

It's not dotnet or even Pulumi specific but I was pointed at this talk from the cloud engineering summit last year that may be of interest: https://www.pulumi.com/resources/reuse-dont-repeat-creating-an-infrastructure-as-code-module-library/

Thanks to both @echoing-dinner-19531 and @bored-oyster-3147 for your additional info. I haven't found or been told more fully formed samples in .NET. I'm planning to start to assemble one. As I get something together, I'll publish it to a repo and I may ping folks here to get some thought on it so we can evolve it into a relatively canonical sample.

If you think it makes sense feel free to raise a PR to add an example to https://github.com/pulumi/examples. We've got a few examples there of using ComponentResources but only one dotnet one so far (https://github.com/pulumi/examples/tree/master/classic-azure-cs-cosmosapp-component)