Lynda Fluent API Development in C Sharp
File List
- 5.4. Refactoring to Fluent/16.Code a fluent API.mp4 28.5 MB
- 3.2. Techniques/10.Extension methods.mp4 6.0 MB
- 3.2. Techniques/08.Generics.mp4 5.8 MB
- 2.1. Why Fluent/03.Defining a fluent interface.mp4 5.7 MB
- 4.3. Existing Fluent APIs/12.Azure Management.mp4 5.4 MB
- 4.3. Existing Fluent APIs/11.LINQ.mp4 5.3 MB
- 3.2. Techniques/07.Using conjunctions.mp4 4.4 MB
- 5.4. Refactoring to Fluent/14.Overview of the console app.mp4 3.7 MB
- 3.2. Techniques/09.Indentation.mp4 3.3 MB
- 5.4. Refactoring to Fluent/15.Diagram a fluent API.mp4 3.2 MB
- 2.1. Why Fluent/04.A quick example.mp4 2.9 MB
- 3.2. Techniques/06.Method chaining.mp4 2.7 MB
- 1.Introduction/01.Welcome.mp4 2.6 MB
- 2.1. Why Fluent/05.Creating paths.mp4 2.5 MB
- 4.3. Existing Fluent APIs/13.Fluent assertions.mp4 2.4 MB
- 6.Conclusion/17.Next steps.mp4 2.1 MB
- 1.Introduction/02.What you should know.mp4 673.8 KB
- Exercise Files/Ex_Files_Fluent_API_Dev_C_Sharp.zip 298.1 KB
- 5.4. Refactoring to Fluent/16.Code a fluent API.en.srt 13.7 KB
- 2.1. Why Fluent/03.Defining a fluent interface.en.srt 7.4 KB
- 4.3. Existing Fluent APIs/12.Azure Management.en.srt 4.0 KB
- 2.1. Why Fluent/04.A quick example.en.srt 3.8 KB
- 3.2. Techniques/10.Extension methods.en.srt 3.4 KB
- 3.2. Techniques/08.Generics.en.srt 3.4 KB
- 4.3. Existing Fluent APIs/11.LINQ.en.srt 3.2 KB
- 2.1. Why Fluent/05.Creating paths.en.srt 3.1 KB
- 3.2. Techniques/07.Using conjunctions.en.srt 3.0 KB
- 5.4. Refactoring to Fluent/14.Overview of the console app.en.srt 2.7 KB
- 3.2. Techniques/09.Indentation.en.srt 2.2 KB
- 3.2. Techniques/06.Method chaining.en.srt 1.9 KB
- 5.4. Refactoring to Fluent/15.Diagram a fluent API.en.srt 1.7 KB
- 4.3. Existing Fluent APIs/13.Fluent assertions.en.srt 1.7 KB
- 6.Conclusion/17.Next steps.en.srt 1.6 KB
- 1.Introduction/01.Welcome.en.srt 1.4 KB
- 1.Introduction/02.What you should know.en.srt 628 bytes
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.