Dotnetguides · published by Mottobits
.NET problems. Practical next steps.
Notes on slow applications, safer releases, and upgrades. Read the approach, check the sources, and use what fits your system.
Written with AI and not reviewed by a human. It may contain mistakes.
Subscribe by RSSStart with your problem
Find your next useful step.
Go deeper
Practical playbooks.
Read the method, inspect the example, and download a copy for your team. No email gate.
Investigate a slow .NET workflow
Locate the cost, choose a targeted measurement, and test one change against the original workload.
AI-generated · 6 MIN READ · PLAYBOOK + DOWNLOADAI QABuild a Playwright harness your AI agents must pass
A client-owned automation suite for critical workflows, with CI evidence, protected test ownership, and enforced review before agent-generated changes merge.
AI-generated · 6 MIN READ · PLAYBOOK + DOWNLOADAI deliveryReview AI-generated tests before they become release evidence
A practical review contract for using AI to draft tests while preserving independent expectations, meaningful assertions, and human ownership.
AI-generated · 4 MIN READ · PLAYBOOK + DOWNLOAD.NET modernizationMove one .NET capability at a time, with a route back
Scope an incremental ASP.NET migration around one capability, explicit compatibility checks, and a rollback decision that includes data.
AI-generated · 5 MIN READ · PLAYBOOK + DOWNLOADDynamics 365A Dataverse timeout leaves the write uncertain.
Read the pinned account row and classify its state before deciding whether to retry.
AI-generated · 11 MIN READ · PLAYBOOK + DOWNLOADFree assessmentCheck your release evidence
Ten questions identify missing checks and useful next actions. Your answers stay in your browser.
NO EMAIL GATE · NO SOURCE UPLOADEngineering notes
Work through a difficult change.
Focused notes on debugging, data access, upgrades, and reviewing AI-generated changes.
A green save test can hide a failed write.
Verify the stored result before approving an Entity Framework Core (EF Core) upgrade.
AI-generatedSame URL. Wrong application.
Test request ownership, generated links and rollback before approving an ASP.NET migration.
AI-generatedTest a SQL Server index against the whole workload
Check whether a proposed index improves the affected operation enough to justify its write, storage, and rollout costs.
AI-generatedMake your Playwright save test prove the data changed
AI-generated tests can pass while a .NET save operation does nothing. Require a known starting value, an independent read, and a failure rehearsal before treating the test as release evidence.
AI-generatedFix the background worker's scope before changing service lifetimes
A scoped-service error needs an ownership fix. Give your coding agent the registrations, work boundary, and checks that prove each job releases its dependencies.
AI-generatedDiagnose a .NET timeout before changing the timeout
Locate the wait, test competing causes, and use runtime evidence to decide what to inspect next.
AI-generatedFind the expensive part of an Entity Framework Core query
Use SQL, command counts, and a representative execution plan to choose between a query change, an index, and an application fix.
AI-generatedA JSON sample can hide a missing required field.
Test missing, null and valid inputs before approving AI-generated C# models.
AI-generatedChoose the first migration slice worth funding
Reject slices that hide shared state or prove too little. Fund one bounded customer workflow and the evidence needed to stop or expand.
AI-generatedAI-generated
About these Fieldnotes.
Written with AI and not reviewed by a human. It may contain mistakes.
Check the linked primary sources and validate any examples against your own requirements before using them. Proposed techniques are not executed tests or client results.
Talk to Mottobits
Need help getting it done?
Mottobits provides dedicated development and QA, SQL Server and .NET performance work, and support for upgrades. Tell us the result you need; we will discuss the scope and price.