SOLID Principles: Part 1 The SOLID principles (Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion), are a set of core object-oriented design principles created by Robert C. Martin. The basic idea behind the inception of these principles is that developers who apply them will end up with code that is easier to extend […]
Test-driven development (TDD) is a concept that I have started utilizing when writing code. If you are unfamiliar with this concept, TDD can simply be described as the practice of developing the tests before coding the actual logic. If you are new to this concept, it may seem backwards to write a test before having any code to run it against, but I have found that writing code this way can help eliminate many potential bugs in your code. In this blog post I will describe the basic process of developing code using TDD, and walk through an example of writing code using this strategy to demonstrate how you can use TDD to write code more effectively. (Note: Mocks, Fakes, Dependency Injection and Inversion of Control will not be discussed since the objective of this post is only to demonstrate the TDD process.)
If you have ever developed a custom master page for SharePoint, you may have been faced with the challenge of trying to add a content editor web part to a master page. You may have researched this and found that it is possible to add a web part directly into your master page, however you would be unable to edit the web part from the browser rendering the content editor web part useless in this scenario. Fortunately, there is a way you can work around this constraint.