Dotnetguides · published by Mottobits
Start with the problem: a slow request, an upgrade that must preserve existing data, or a release that needs better evidence. Find a guide below to help your engineers scope the work and decide what to check.
Engineering guides
Written with AI and not reviewed by a human. It may contain mistakes.
Investigate .NET timeouts, EF Core queries and SQL Server indexes. Use measurements to choose the next change.
An AI-generated index can make one slow query look convincing. The release decision is harder: will it shorten the wait for order searches without making order entry, imports, and routine updates too expensive?
Read the guideFollow one failing operation through the application and its dependencies. Use the evidence to decide which change deserves engineering time, and whether a longer wait would help at all.
Read the guideStart with one search people rely on. Measure what the application fetches, how many database calls it makes, and what users wait for before choosing a query change or more capacity.
Read the guideTurn one slow business feature into a bounded measurement experiment. Agree what improvement matters, test one explanation, and use the result to decide whether to release a change or invest further.
Read the guideChoose a first .NET feature to move, then plan route ownership, shared data and the period when old and new applications coexist.
A .NET migration can pass its traffic-switch test and still lose data on the next legacy edit. Preserve the shared document, then rehearse the complete write-back path.
Read the guideKeep customers working. Keep shipping features and improvements. Roll out gradually, with a tested path back to legacy.
Read the guideUse existing records to decide whether an ORM upgrade is ready, and keep database changes deliberate.
Read the guideThe easiest screen to rewrite may deliver little value. Choose a first feature with a recognizable payoff, a manageable dependency boundary and evidence that will help decide the next investment.
Read the guideMoving the first feature creates a second responsibility: operating two applications while the product continues to change. Make ownership, shared-state rules and the end of temporary support part of the delivery plan.
Read the guideReview AI-generated tests, capture legacy business rules and check whether a saved change survives.
Use Playwright to check what the application retained and who was allowed to change it.
Read the guideA regression harness checks agreed business behavior before and after a change. Start with one operation and assess the setup it needs.
Read the guideAI can help produce tests quickly. Before relying on them, demonstrate that important checks fail when the implementation breaks an agreed business rule.
Read the guideReview C# request contracts, background job scopes and handled-exception diagnostics in ASP.NET Core.
An exception handler can return an error response while its middleware stops logging the exception. Choose which failures should retain diagnostic detail, and test the signals your alerts actually consume.
Read the guideGive each order import its own dependency scope, then check disposal and overlapping work before increasing throughput.
Read the guideSeparate missing fields, explicit nulls, and invalid business values so an AI-generated C# model enforces the contract your callers expect.
Read the guideDecide what to check after a Dynamics 365 write times out, before replaying the request.
Suppose an external system sends a new customer to Dynamics 365 Sales, but its response never arrives. Support must establish whether the customer exists and whether replaying the request would repeat other work.
Read the guideEngineering tools
These tools run in your browser. They do not inspect code or approve a release.
Talk to Mottobits
Discuss dedicated development and QA, .NET performance, or an upgrade with Mottobits.
