Pluralsight - Designing Fluent APIs in C Sharp
File List
- 04. Case Study Fluent Testing of INotifyPropertyChanged/04_02-Adding a Simple Fluent Call.mp4 26.7 MB
- 05. Case Study FluentMapper/05_03-Hiding Implementation Details.mp4 23.4 MB
- 04. Case Study Fluent Testing of INotifyPropertyChanged/04_03-Refactoring to Accommodate Negative Tests.mp4 20.5 MB
- 05. Case Study FluentMapper/05_02-New Pattern Context Arc.mp4 19.6 MB
- 02. Designing Fluent APIs in C/02_01-The Benefits of Fluent APIs.mp4 19.0 MB
- 04. Case Study Fluent Testing of INotifyPropertyChanged/04_04-Exclusive Notification Verification.mp4 14.1 MB
- 04. Case Study Fluent Testing of INotifyPropertyChanged/04_01-Path to the First Passing Test.mp4 13.0 MB
- 03. Identifying the Components of Fluent APIs/03_02-Characteristics of Fluent APIs.mp4 12.6 MB
- 05. Case Study FluentMapper/05_04-A Completed Context Arc.mp4 11.5 MB
- 03. Identifying the Components of Fluent APIs/03_03-Components of Fluent APIs.mp4 11.4 MB
- 05. Case Study FluentMapper/05_01-The Path to the First Working Test.mp4 10.5 MB
- 04. Case Study Fluent Testing of INotifyPropertyChanged/04_05-Recap.mp4 9.6 MB
- 02. Designing Fluent APIs in C/02_04-Collaboration and Refinement of Fluent API Drafts.mp4 7.8 MB
- 02. Designing Fluent APIs in C/02_03-Domainspecific Languages and Fluent APIs.mp4 7.6 MB
- 03. Identifying the Components of Fluent APIs/03_05-Recap.mp4 7.1 MB
- 03. Identifying the Components of Fluent APIs/03_04-Type Inference and Verbose Method Signatures.mp4 5.8 MB
- 01. Course Overview/01_01-Course Overview.mp4 4.4 MB
- 02. Designing Fluent APIs in C/02_02-Course Synopsis.mp4 3.9 MB
- 02. Designing Fluent APIs in C/02_05-Feedback, Tests, and Documentation.mp4 3.6 MB
- 03. Identifying the Components of Fluent APIs/03_01-Method Chaining.mp4 3.4 MB
- 02. Designing Fluent APIs in C/02_06-Recap.mp4 3.1 MB
- Exercise files/designingfluentapiscsharp.zip 778.3 KB
Download Torrent
Related Resources
Copyright Infringement
If the content above is not authorized, please contact us via anywarmservice[AT]gmail.com. Remember to include the full url in your complaint.