If you’re building TypeScript frontend solutions with a .NET backend or you have a setup where you need to have the same models in some TypeScript code (e.g. same model definitions in a TypeScript…

ITNEXT is a platform for IT professionals, developers, and technology enthusiasts, offering articles, tutorials, and insights on a wide range of topics, including software development, cloud computing, and machine learning. With a focus on practical solutions and real-world applications, ITNEXT provides actionable advice and best practices for navigating the complexities of modern technology landscapes. Developers can learn about  technologies, explore hands-on tutorials, and stay up-to-date on the latest industry trends through ITNEXT's engaging and informative content.

ITNEXT

Learn how to achieve end-to-end type safety with .NET 7 Web APIs, TypeScript, and OpenAPI. Set up the frontend and backend configurations, generate OpenAPI schema and TypeScript client bindings, and enable hot reload for development.

End-to-End Type Safety with .NET 7 Web APIs, TypeScript, and OpenAPI

<p>Very nice! Makes me feel like finding a way to integrate this into our stack at work…it pains me to have to write models in C# for the backend (with <code>JsonProperty</code> attributes) and then write corresponding TypeScript models in the frontend…but sadly our setup is a lot more complicated than in this article and I don’t have the time to implement something like this :-\ .</p>
