Plan to study the course:
Become a Full-stack .NET Developer - Architecture and Testing
Lecturer's website:
http://app.pluralsight.com/author/mosh-hamedani
Notes:
1. Remaining use cases
2. Modularize JavaScript Code
3. Refactoring towards the clean architecture
4. Programming against interfaces
5. Test Controllers
6. Test Repositories
7. Adding Integration Tests
Modularizing JavaScript Code - 40m 56s
Introduction
Extracting JavaScript Code
Revealing Module Pattern
Refactoring using Revealing Module Patten
Cleaning the init Method
Applying the DRY Principle
Better Separation of Concerns
Module Dependencies
Physical Separation
Optimization
Exercise
Code Review
Summary
Programming Against Interfaces
Introduction
Dependency Inversion Principles
Extracting Interfaces
Dependency Injection
Adding Ninject
Does Entity Framework Really implement the Repository Pattern?
Package Dependencies
Restructure the Application
Complexity Fallacy
Productivity Fallacy
Exercise
Refactoring Data Annotations
Complexity Fallacy
Productivity Fallacy
Exercise
Refactoring Data Annotations
Summary
Testing Controllers
Introduction
Extracting Queries
Repository pattern
When to use the repository pattern
extracting repositories
extracting queries with eager loading
exercise
code review
clean architecture
decoupling from entity framework
unit of work pattern
implementing the unit of work
consolidating dependencies
summary
Programming Against interfaces
introduction
Dependency inversion principle
extracting interfaces
Repository pattern is already in entity framework - no need to use? it depends.
Design to solve problems - repository pattern
complexity of design - be pragmatic
meidum/ large projects
problems :
complex queries/ fat controllers/ fat services
SQL Injection etc. website common attacks -
SQL injection, XSS, CSRF, preventing CSRF attacks -
http://www.veracode.com/security/xss
No comments:
Post a Comment