Notes from Creating N-Tier Applications in C#, Part 2 Pluralsight Course
Date Published: October 20, 2020
Steve Smith's Pluralsight course Creating N-Tier Applications in C#, Part 2 goes into more detail about N-Tier Applications.
I recently completed Creating N-Tier Applications in C#, Part 2 by Steve Smith.
Here are my notes from Creating N-Tier Applications in C#, Part 1.
Here are my notes from Part 2:
- Unit tests in an n-tier application should generally only care about one of your tiers (which should be in its own project file); integration tests will likely care about several tiers, and possibly also have some external dependencies on databases, etc.
- Mocks are a useful tool in unit tests, but should generally be used for tests of behavior, rather than tests of state
- If you're working in a shared repository, you should run all tests before checking in (also, make sure you're using the latest version and make sure your code builds)
Core Logic Reuse
"Holy Grail of Software" = code reuse
- software components should be like LEGOs
Dependency Inversion Principle -> depend on interfaces, not specific implementation
- related to IOC containers, which are essentially "factories on steroids"
- aids code reuse
- DTO = Data Transfer Object - typically a class full of data, no behavior
Thanks for reading! I hope you find this and other articles here at ilyanaDev helpful! Be sure to follow me on Twitter @ilyanaDev.