dotnet

Best practices for using MSBuild traversal projects

Use vertical slices / features as an organization mechanism and make Directory.Build.props and .targets files easier to work with

Recently, I was writing a .NET console app to integrate with a third-party library and had an opportunity to use the IOptions pattern. However, the settings object didn’t have a public, parameterless constructor. Here’s how I used IOptionsFactory to support these types of options classes…

Create a custom attribute to extend MSTest to programmatically skip / ignore tests based on factors like OS or framework version

I seem to have hit some sort of edge case between the Castle DynamicProxy object and the binding / dispatching of method calls in PowerShell.