How to Migrate .NET 8 APIs to .NET 10 Without Breaking Consumer Contracts

·8 views

Microsoft has confirmed that .NET 8 and .NET 9 will reach end of support on November 10, 2026, making .NET 10 the recommended long-term support target for developers. Experts advise treating the upgrade as an API contract migration rather than a simple project-file change, since a service can compile and pass unit tests while still delivering altered JSON shapes, status codes, or authentication responses to consumers. The recommended approach separates the migration into three distinct phases: updating the SDK and target framework, refreshing NuGet dependencies, and updating runtime infrastructure, so failures are easier to isolate. Before retargeting, developers are urged to write focused contract tests covering observable HTTP behaviors such as status codes, content types, and required JSON fields using tools like xUnit and WebApplicationFactory. Microsoft provides an official .NET 10 WebApplicationFactory sample as a reference for test-host setup, and a published breaking-change catalog to guide developers beyond what compiler errors alone reveal.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

BMW Displays Full-Screen Ads on In-Car Dashboard Screens

BMW has begun showing full-screen advertisements on the main dashboard display of its vehicles. The ads have appeared on the central infotainment screen, which drivers typically rely on for navigation and vehicle controls. A Spider-Man promotional ad was among the examples documented and reported via a consumer rights wiki. The practice has drawn attention and criticism from car owners and online communities concerned about distraction and user experience. This raises broader questions about automakers monetising in-car screens through third-party advertising.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

DocFence 0.1.0 Brings CI Pipeline Checks to Word Document Reviews

DocFence 0.1.0 is a newly released open-source tool designed to apply continuous integration boundaries to Microsoft Word document reviews. The tool inspects .docx and .docm files by analyzing stored OOXML content rather than Word's rendered output, covering elements such as macros, custom XML, hidden text, and unresolved revisions. Users define review policies through a short YAML configuration file, and the tool exits with a nonzero code when a violation is detected, with SARIF output supported for integration into CI pipelines. DocFence is installable via pip from its GitHub releases page and offers commands for diffing documents and running policy checks. The project is MIT-licensed and publicly available on GitHub.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Insufficient source content to generate a reliable summary

The provided source contains no article body — only a URL, comment link, and engagement metrics. No factual content is available to summarize accurately. Fabricating details from the headline alone would violate editorial integrity standards. Please provide the full article text for proper processing.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Developer shares five hard lessons building a GPU-free, on-premise RAG system for public sector

A developer working on public sector health information systems built a fully on-premise retrieval-augmented generation (RAG) stack that runs on CPU-only Windows Server hardware without Docker or cloud access. The open-source system uses ASP.NET Core 9, Ollama, Qdrant, Mistral 7B, and a Python ingest pipeline to process and query PDF, Word, and Excel documents locally. The project was motivated by strict institutional data-residency requirements common in healthcare and government environments, where modern AI infrastructure assumptions rarely apply. During deployment, the developer encountered five significant issues not covered in standard RAG tutorials, including gRPC incompatibility with HTTP/1.1-only corporate networks, which required bypassing the official Qdrant .NET SDK in favour of direct REST API calls. The field report is intended to help others facing similar legacy enterprise constraints where GPU access and cloud connectivity cannot be taken for granted.

0 comments Read more at DEV Community