Andrew

@Devvox93 I agree that ResourceType should be a string parameter with a ValidationSet of Unspecified (don't think this is an option in the UI but is in handler documentation), File,...

Although I've updated the tests project it seems like it's missing a packages.config file required to reference nunit. After adding this reference some of the tests were failing, I've reverted...

When empty it should use the following cmdlet Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ResetServerAddresses This mimics the Windows UI functionality in that if DHCP is enabled DNS is set to automatic, if...

@PlagueHO Having a skim over this it looks great so far, will hopefully get a chance to test some week sometime (deadlines are pretty tight over here). Thanks!

Will test this week, thanks @PlagueHO

Sorry @PlagueHO been a busy free months! Managed to test this today and worked as expected. Tested the standard use cases and the following edge cases with IPv4: - 3+...

Same issue exists in PSDscResources, should I raise on that repo too? I haven't looked at this in depth but is there perhaps a culture invariant format? A quick google...

Thanks for the quick response, that answered my questions on the delivery callbacks. In regards to the IProduer instance methods, is calling `IProducer.Produce("topic", message, deliveryCallback)`, `IProducer.Flush()` and `IProducer.Dispose()` on separate...

Thanks for your assistance. To summarise: - After constructing a IProducer, calling Flush/Produce is thread safe. - In Delivery Handler callback implementations it's safe to assume that the IProducer is...

@mhowlett > it's not safe to call any method after you've called `Dispose`. all the produce methods and flush are threadsafe. I assume if Dispose is called and completes, invocations...