Why I love Resharper 3
Learning new language features can be hard. Applying them can be tricky. How does Resharper aid with filescoped namespaces?
Learning new language features can be hard. Applying them can be tricky. How does Resharper aid with filescoped namespaces?
Using the Arrange, Act, Assert setup in unit tests, why do I still add the comments? Read on to find out.
Looking at another constructor parameter checking option when passing in an enum value.
Refactoring to use the Decorator Design Pattern to help apply the Single Responsibility Principle.
Adding strongly typed configuration settings and injected them through dependency injection.
Starting the journey of going past the basics of beginner training resources to appy software development practices and design patterns.
Looking at how newer language features allow for extension of types to add Deconstruct functionality.
Reducing the coupling of code dependent on DateTimeOffset
With every new version of C# a new version of Resharper appears. It teaches me the new language features and how I can write my code in the new way. It’s not always right as the code it converts to can be unmaintainable so you have to be careful. But every now and then it makes me realise why I pay for a great productivity tool. public FeatureController(ApplicationDbContext applicationDbContext) { if (applicationDbContext == null) { throw new ArgumentNullException("applicationDbContext", "Argument cannot be null....
Going through my old repositories on Github made me realise I’d forgotten about a number of coding items I have done in the past. There was one which was a coding Kata originally created by Scott Allen around refactoring. Refactoring is the ability to improve code readability to increase its simplicity and maintainability. If you write code that the rest of your development team can’t understand or spends 10 times as long to understand before they can alter it then it’s failed....