Recent posts tagged dotnet

Description for Tag: "dotnet"

A free, open-source developer platform used for building different types of applications.
Level UI • 18 hours • in Articles • 9 min read
Somewhere in the last year, "do we need an MCP server?" joined the list of questions that arrive in a brief before anyone has said what the thing is for. It is usually framed as MCP vs API, as though the Model Context Protocol were a newer kind of AP...
post-cover-33074
  • ai
  • api
  • webdev
  • security
jeff377 • 4 hours • in Articles • 12 min read
The previous post, Why ERP Needs a Definition-Driven Frameworkhttps://coderlegion.com/33030/day-1-why-erp-needs-a-definition-driven-framework, ended by promising this one would be about which decisions a framework should make on its users' behalf. T...
post-cover-33157
  • dotnet
  • architecture
  • erp
  • software-engineering
Bansi Sojitra • 23 hours • in Articles • 3 min read
As a full stack developer, I’ve learned that building a web application is not just about writing code or choosing the right framework. It’s about understanding problems, finding practical solutions, and making sure everything works together smoothly...
  • webdevelopment
  • dotnet
  • fullstackdevelopment
jeff377 • 1 day • in Articles • 4 min read
> The complexity of an ERP is not in how hard any single feature is. It is in how many times the same fact gets restated, multiplied by how many tables, multiplied again by how many customizations. A thirty-post series written for iThome Ironman 202...
post-cover-33029
  • dotnet
  • architecture
  • erp
  • software-engineering
jeff377 • 1 day • in Articles • 15 min read
This is the first post in a thirty-part series, ERP Architect's Notes: Designing a Definition-Driven Framework. What follows is not about building one form with some framework. It is about designing a framework that can drive hundreds of forms: whic...
post-cover-33030
  • dotnet
  • architecture
  • erp
  • software-engineering
jeff377 • 1 day • in Articles • 11 min read
JSON-RPC 2.0 is a small specification: the client sends {"jsonrpc":"2.0","method":"...","params":{...},"id":1}, and the server answers with a result or an error. REST makes you decide on routes, HTTP verbs and status codes; JSON-RPC only cares about ...
post-cover-32964
  • dotnet
  • csharp
  • aspnetcore
  • opensource
Ivan Rossouw • 2 days • in Articles • 4 min read
Timing tests look wonderfully objective. Start a stopwatch, call the component, stop the watch, and compare the result with a budget. The number is precise. The experiment may not be. That distinction matters in continuous integration, where many t...
  • dotnet
  • testing
  • devops
  • reliability
Spyros • 3 days • in Articles • 1 min read
When building enterprise applications in C#, a common architectural trap is writing procedural code disguised as object-oriented code. This usually happens when we rely entirely on anemic data bags public get; set; DTOs for business logic, forcing ou...
  • csharp
  • dotnet
  • oop
  • cleanarchitecture
Posted in .NET Community group
Jakub Neruda • 3 days • in Articles • 1 min read
Tuesday coding tips are super short posts about various tidbits mainly from C++, but also from other programming languages I use. You can also follow the #TuesdayCodingTips hashtag on Mastodon and Linkedin. Last time I covered C# JSON serialization,...
  • tuesday-coding-tips
  • dotnet
  • csharp
Ivan Rossouw • 4 days • in Articles • 4 min read
Software often uses broad time windows for good reasons. A dashboard may need recent history, work that is actionable now, and the next scheduled item. Fetching all of that in one bounded query can be efficient and easy to reason about. The trouble ...
  • dotnet
  • csharp
  • testing
  • reliability
Ivan Rossouw • 5 days • in Articles • 4 min read
Idempotency is usually introduced with a simple promise: run the operation again and it will not create a duplicate. That promise is useful, but it can become dangerous when we apply it to an entire workflow instead of the specific durable step it p...
  • dotnet
  • csharp
  • architecture
  • reliability
Ivan Rossouw • 6 days • in Articles • 4 min read
Navigation bugs are often judged by their final state. Did the correct page appear? Did the authorization check pass? Did the URL settle on the expected address? Those questions matter, but they can miss the frame that users actually notice. In a r...
  • blazor
  • dotnet
  • webdev
  • testing
Ivan Rossouw • Oct 23 • in Articles • 4 min read
A release verifier has two jobs that are easy to blur together. It must understand the representation produced by the build chain, and it must enforce the policy that decides whether an artifact may leave that chain. Those jobs need different attitu...
  • dotnet
  • mobile
  • devops
  • testing
Ivan Rossouw • Oct 22 • in Articles • 4 min read
An empty form field looks unimportant. In ordinary application logic, treating an empty value like a missing value is often reasonable. In signature verification, that assumption can reject a legitimate message—or, in a different protocol, verify a r...
  • dotnet
  • csharp
  • security
  • testing
Ivan Rossouw • Oct 21 • in Articles • 4 min read
Many concurrency bugs begin with code that looks entirely reasonable: 1. Read the current row. 2. Check that the operation is still allowed. 3. Create something durable elsewhere. 4. Save the original row as complete. Run once, the workflow is corr...
  • dotnet
  • csharp
  • efcore
  • architecture
Ivan Rossouw • Oct 20 • in Articles • 4 min read
Flaky lifecycle tests often produce a tempting diagnosis: the cleanup code must be unreliable. Sometimes that is true. Sometimes the test is asking a framework harness to prove a narrower ownership contract, and the harness is free to finish work on ...
  • dotnet
  • blazor
  • testing
  • csharp
Spyros • Oct 19 • in Articles • 1 min read
For years, C# interfaces were limited strictly to instance members. If you wanted to define a contract requiring a class or struct to implement a static method like a string parser or a factory method you had to rely on reflection, runtime type che...
  • c#
  • dotnet
Ivan Rossouw • Oct 18 • in Articles • 4 min read
Moving a user from one application host to another often looks harmless. A button opens a browser, the user continues, and the original client waits for them to return. Architecturally, that is not merely navigation. It is a trust-boundary decision....
  • dotnet
  • blazor
  • security
  • architecture
Ivan Rossouw • Oct 17 • in Articles • 4 min read
Soft deletion often begins innocently: add an IsDeleted flag, remember to exclude retained rows, and move on. That works until the application grows into several modules, several DbContext types, and configuration spread across assemblies. At that p...
  • dotnet
  • efcore
  • csharp
  • architecture
Ivan Rossouw • Oct 16 • in Articles • 4 min read
Background work is usually introduced to make a system more reliable. We persist an intent, let the request finish, and deliver the external side effect later. That protects the user-facing path from temporary provider failures and gives us room for ...
  • dotnet
  • reliability
  • architecture
  • testing
Ivan Rossouw • Oct 15 • in Articles • 4 min read
Two projects expose similar helpers. One has no project references. It is missing from the solution most developers build every day. The obvious reaction is understandable: share the code, add the reference, and bring the lonely project back into the...
  • dotnet
  • maui
  • architecture
  • testing
chevron_left
🔥 104 posts • 👩‍💻 38 active writers

✨ Want to write in this topic?
Share your learning. Get discovered. Build your profile.
Join CoderLegion

💡 Why developers use CoderLegion
Track learning • Share posts • Get ranked publicly
Create your profile