<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mervenor</title>
    <description>The latest articles on DEV Community by Mervenor (@mervenor).</description>
    <link>https://dev.to/mervenor</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4247231%2F01298e40-8c57-40f8-9004-32ebc6a97dda.png</url>
      <title>DEV Community: Mervenor</title>
      <link>https://dev.to/mervenor</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mervenor"/>
    <language>en</language>
    <item>
      <title>Your developer disappeared: a 10-step recovery checklist</title>
      <dc:creator>Mervenor</dc:creator>
      <pubDate>Mon, 16 Nov 2026 08:52:52 +0000</pubDate>
      <link>https://dev.to/mervenor/your-developer-disappeared-a-10-step-recovery-checklist-399o</link>
      <guid>https://dev.to/mervenor/your-developer-disappeared-a-10-step-recovery-checklist-399o</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://mervenor.com/guides/developer-disappeared-checklist" rel="noopener noreferrer"&gt;mervenor.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If your developer or agency has gone, recover access before you change anything. Get the domain, the hosting, the code and the accounts into your name, in that order, and then change every password and key the previous developer knew. Only then decide what to fix, with an independent review of what you have.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you start
&lt;/h2&gt;

&lt;p&gt;When the developer or agency who built your application goes quiet, the instinct is to hire someone to fix the code. Start one step earlier: the code is only useful once you control everything around it — the domain, the hosting, the repository, the secrets and the services it depends on.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 10 steps
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Do not change anything yet&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Write down what you know: the address of the app, who used to work on it, and which emails and invoices mention its services. Changes made in a hurry are the hardest to undo.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Find the domain&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Look up who the domain is registered to and at which registrar. If it is not in your company's name, ask for it to be transferred first: whoever holds the domain controls your website and your email.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Get the hosting account&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Find where the app runs and whose card pays for it. Ask for the account to be transferred to you, or for you to be added as an owner.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Get the code&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Ask for the source code repository to be transferred to an account you own. If it cannot be found, part of it can be rebuilt from what is deployed (see below).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Collect the secrets&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Passwords, API keys, database credentials and environment settings. Keep them in a password manager your company controls.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. List every third-party service&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Email sending, payments, analytics, maps, app stores, error tracking. For each one: who owns the account, who pays, and what breaks if it stops.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7. Change the keys the previous developer knew&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Once you hold them, change the passwords and API keys, starting with payments, email and the database. Plan a quiet window: some changes need a release.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;8. Check the backups&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Find out whether the database is backed up, where, and when the last backup ran. Then restore one to a test environment to prove it works.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;9. Find out how it is built and released&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Can the app be built from a clean machine? Where do releases run from? If nobody knows, that is the first thing to fix.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;10. Get an independent review before new work&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Before anyone adds features, have the codebase reviewed: what is risky, what is out of date, and what it will cost to make it safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  If the code is missing
&lt;/h2&gt;

&lt;p&gt;Part of an application can often be rebuilt from what is deployed: the running site, build artefacts, the database schema and the hosting configuration. It is slower than recovering the repository and never complete, so ask for the repository first, in writing.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to bring in help
&lt;/h2&gt;

&lt;p&gt;Bring someone in once you have the accounts, or as soon as you are stuck on one. A good first engagement is read-only: a review of what you have and a plan, before anyone changes it.&lt;/p&gt;




&lt;p&gt;We are Mervenor: we take over, fix and modernise existing web applications. The full guide, with related guides, is at &lt;a href="https://mervenor.com/guides/developer-disappeared-checklist" rel="noopener noreferrer"&gt;mervenor.com/guides/developer-disappeared-checklist&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>startup</category>
      <category>security</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Upgrading .NET 8 or 9 to .NET 10: the checklist</title>
      <dc:creator>Mervenor</dc:creator>
      <pubDate>Mon, 16 Nov 2026 08:52:39 +0000</pubDate>
      <link>https://dev.to/mervenor/upgrading-net-8-or-9-to-net-10-the-checklist-38am</link>
      <guid>https://dev.to/mervenor/upgrading-net-8-or-9-to-net-10-the-checklist-38am</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://mervenor.com/guides/upgrade-dotnet-8-to-10" rel="noopener noreferrer"&gt;mervenor.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;For most applications, moving from .NET 8 or .NET 9 to .NET 10 is a contained piece of work: new tools, a new target framework, updated packages and the breaking changes that touch your code. Support for .NET 8 and .NET 9 ended on 10 November 2026, and .NET 10 is supported until 14 November 2028. Do it on a branch, release through a test environment, and keep the previous build ready to restore.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you start
&lt;/h2&gt;

&lt;p&gt;List every project in the solution with its target framework, every service, function and scheduled job, and where each one runs. Note the SDK version pinned in &lt;code&gt;global.json&lt;/code&gt;, the images your containers start from, and the SDK on your build agents. Make sure the test suite runs green on .NET 8 first: an upgrade on top of failing tests hides its own breakages.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Update the tools
&lt;/h2&gt;

&lt;p&gt;Install the .NET 10 SDK on every developer machine and build agent, and update &lt;code&gt;global.json&lt;/code&gt; if it pins the SDK. Use an IDE version whose release notes list .NET 10 support. Update the build pipeline's setup step and any &lt;code&gt;dotnet&lt;/code&gt; tools the build installs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Change the target framework
&lt;/h2&gt;

&lt;p&gt;Change the target framework in each project file, or once in &lt;code&gt;Directory.Build.props&lt;/code&gt; if the solution sets it there:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;TargetFramework&amp;gt;&lt;/span&gt;net10.0&lt;span class="nt"&gt;&amp;lt;/TargetFramework&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Libraries that other applications still consume on .NET 8 can multi-target for a while (&lt;code&gt;&amp;lt;TargetFrameworks&amp;gt;net8.0;net10.0&amp;lt;/TargetFrameworks&amp;gt;&lt;/code&gt;) and drop &lt;code&gt;net8.0&lt;/code&gt; when the last consumer has moved. C# 14 becomes the default language version with &lt;code&gt;net10.0&lt;/code&gt;; you do not have to use its new features.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Update the packages
&lt;/h2&gt;

&lt;p&gt;Move the Microsoft packages (&lt;code&gt;Microsoft.AspNetCore.*&lt;/code&gt;, &lt;code&gt;Microsoft.EntityFrameworkCore.*&lt;/code&gt;, &lt;code&gt;Microsoft.Extensions.*&lt;/code&gt;) to their 10.0 versions together, then check each third-party package for a release that supports .NET 10. &lt;code&gt;dotnet list package --outdated&lt;/code&gt; gives the starting list. In .NET 10, &lt;code&gt;dotnet restore&lt;/code&gt; also audits transitive packages for known vulnerabilities, so expect new warnings the first time: treat each one as a finding, not as noise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Work through the breaking changes
&lt;/h2&gt;

&lt;p&gt;Microsoft publishes the full lists for .NET 10, ASP.NET Core 10 and EF Core 10; read the entries that touch your code. The ones that most often affect web applications and APIs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;WebHostBuilder&lt;/code&gt;, &lt;code&gt;IWebHost&lt;/code&gt; and &lt;code&gt;WebHost&lt;/code&gt; are obsolete: move to &lt;code&gt;WebApplication&lt;/code&gt; or the generic host.&lt;/li&gt;
&lt;li&gt;Razor runtime compilation is obsolete.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;IActionContextAccessor&lt;/code&gt; and &lt;code&gt;ActionContextAccessor&lt;/code&gt; are obsolete.&lt;/li&gt;
&lt;li&gt;Cookie login redirects are disabled for known API endpoints: an API that used to redirect an unauthenticated request to a sign-in page now answers with a status code, which clients may need to handle.&lt;/li&gt;
&lt;li&gt;The &lt;code&gt;WithOpenApi&lt;/code&gt; extension method is deprecated.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;IPNetwork&lt;/code&gt; and &lt;code&gt;ForwardedHeadersOptions.KnownNetworks&lt;/code&gt; are obsolete, which matters for applications behind a proxy or load balancer.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;BackgroundService&lt;/code&gt; runs all of &lt;code&gt;ExecuteAsync&lt;/code&gt; as a task, so startup code placed there behaves differently.&lt;/li&gt;
&lt;li&gt;Null values are preserved in configuration, and &lt;code&gt;System.Text.Json&lt;/code&gt; checks for property name conflicts.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;"Obsolete" produces a warning, not an error, unless the build treats warnings as errors; plan to remove each one rather than suppress it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Containers and hosting
&lt;/h2&gt;

&lt;p&gt;The default .NET 10 container images, such as &lt;code&gt;mcr.microsoft.com/dotnet/aspnet:10.0&lt;/code&gt;, are based on Ubuntu 24.04 instead of Debian, and Microsoft no longer provides Debian images for .NET 10. Test any Dockerfile step that installs operating-system packages. On Linux, .NET 10 needs OpenSSL 1.1.1 or later. On a managed host such as Azure App Service, change the runtime stack to .NET 10 in a staging slot first.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Test what the build does not catch
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Sign-in:&lt;/strong&gt; API endpoints that relied on cookie redirects, and anything behind a proxy that reads forwarded headers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Background work:&lt;/strong&gt; hosted services and scheduled jobs, including their behaviour at startup and shutdown.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Configuration and serialisation:&lt;/strong&gt; settings that may now arrive as null, and JSON payloads with similar property names.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Telemetry:&lt;/strong&gt; the default trace context propagator is now the W3C standard, so check traces still join up across services.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Speed:&lt;/strong&gt; compare response times and memory before and after on a realistic load.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 7: Roll out safely
&lt;/h2&gt;

&lt;p&gt;Deploy to a test environment that mirrors production and run the full test suite against it. Release to production at a quiet time with the previous build ready to restore in one step, then watch errors, response times and memory for a few days. Move internet-facing services and anything that handles payments or personal data first.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions people ask
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Can we go straight from .NET 6 or 7?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes, with the same steps, but read the breaking changes for each version in between (.NET 8, 9 and 10), not only the last one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Should we go to .NET 11 instead?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;.NET 11 was released on 10 November 2026 as a standard-term release, supported until 14 November 2028, the same day as .NET 10. The steps are the same; for most business applications .NET 10, the long-term-support release, is the steadier target because libraries and hosts have supported it for a year.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. How long does the upgrade take?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It depends on the number of projects and services, the third-party packages, and how much the tests cover. The lists in steps 3 to 5 are the best early estimate of the work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://learn.microsoft.com/en-us/dotnet/core/compatibility/10" rel="noopener noreferrer"&gt;Microsoft Learn, "Breaking changes in .NET 10"&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://learn.microsoft.com/en-us/aspnet/core/breaking-changes/10/overview" rel="noopener noreferrer"&gt;Microsoft Learn, "Breaking changes in ASP.NET Core 10"&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://learn.microsoft.com/en-us/dotnet/core/compatibility/containers/10.0/default-images-use-ubuntu" rel="noopener noreferrer"&gt;Microsoft Learn, "Default .NET images use Ubuntu"&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://endoflife.date/dotnet" rel="noopener noreferrer"&gt;endoflife.date, .NET release and support dates (read 12 Nov 2026)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://devblogs.microsoft.com/dotnet/dotnet-8-9-end-of-support/" rel="noopener noreferrer"&gt;Microsoft .NET Blog, ".NET 8 and .NET 9 will reach End of Support on November 10, 2026" (29 June 2026)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;We are Mervenor: we take over, fix and modernise existing web applications. The full guide, with related guides, is at &lt;a href="https://mervenor.com/guides/upgrade-dotnet-8-to-10" rel="noopener noreferrer"&gt;mervenor.com/guides/upgrade-dotnet-8-to-10&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>dotnet</category>
      <category>csharp</category>
      <category>aspnetcore</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
