delivery-sdk-net

Kontent.ai .NET delivery SDK

Best practices

• ✔️ Use Dependency Injection for better app design
• ✔️ Use HttpClientFactory for increased performance and stability of your app
• ✔️ Use strongly-typed models for all the 10 advantages described here
• ✔️ Use the code generator to automate things and avoid errors
• ✔️ Use partial classes for extending the models & not mess up the generated ones
• ✔️ Use structured rich-text rendering to enable display templates for rich-text elements
• ✔️ Enable retry logic to ensure maximum resiliency of your app
• ✔️ Secret Manager or Azure Key Vault to store Secured Content and Preview API keys

Full Table of Contents

• Configuration
  • Registering the DeliveryClient to the IServiceCollection in ASP.NET Core
  • Accessing data from multiple environments at the same time using named clients
  • Retry capabilities
  • Delivery options explained
• Retrieving data
  • Querying content items
  • Enumerating all items
  • Retrieving secured and previewing unpublished content
  • Using the Kontent.Ai.Delivery.Rx reactive library
  • Caching responses
  • Using the Image transformations
• Customization and extensibility
  • Resolving links to content items
  • Structured Rich text rendering
  • String-based rendering of linked items in Rich text elements
  • Working with strongly typed models
    • 10 Advantages of strong types
    • Generating models
    • DataAnnotations attributes
    • Model Inheritance
    • Runtime Typing
  • Support for custom types in models via Value Converters
  • Retrieve modular content from API response
  • Partial class customization techniques
• Unit testing
  • Faking responses
• Repository practices
  • Release & version management
  • Kontent.ai best practices for .csproj files
• Tools using SDK
  • Source tracking header
• Troubleshooting
  • Using Source Link for debugging

This site is open source. Improve this page.