Debug On Web

Recent Posts

• April 2021 How to enforce a Validation Rule when converting leads?

  Salesforce

• April 2021 How to Send Email Notification to Contact Email on Lead Conversion

  Salesforce

• January 2021 V LOOKUP in Microsoft Excel

  Excel

• January 2021 How to Create Lightning Component Tab in Salesforce

  Salesforce

• January 2020 Bootstrap DateTimePicker using Angular JS in ASP.NET MVC

  Angular JS, ASP.NET MVC

• February 2019 Email and Phone Number Validation in Angular JS

  Angular JS

• December 2017 Events in C#

  C#

• November 2017 Angular Js Events

  Angular JS

Debug On Web is a long-running collection of programming articles aimed at working developers, programmers and coders who need practical answers rather than marketing fluff. The library spans a broad technology mix, from Microsoft .NET and ASP.NET MVC to client-side work with Angular, jQuery, Knockout and Backbone, alongside SQL, REST, WCF and Windows service topics. Each entry is written as a focused walkthrough with sample code so readers can copy a pattern, adapt it to their own project and move on without wading through filler.

The site also carries a substantial question and answer archive, the kind of resource that fills the gap between a textbook explanation and a working solution. Developers arrive with concrete problems drawn from everyday work — enforcing validation rules during lead conversion, setting contact identifiers, sending a single email message, working with standard objects and lookup fields — and the answers unpack the reasoning behind the fix. Browsing that archive is a fast way to find a known solution or to recognise a familiar situation described from another angle.

Salesforce development forms a notable pillar of the content, with posts covering Lightning components, Apex triggers, tabs, approval workflows and custom entities. These tutorials tend to approach the platform from the perspective of someone who has actually implemented the feature in production, which shows in the attention to small details: naming conventions for handlers, the order in which records are queried, and how to surface errors back to the user instead of silently failing. That practical emphasis is the common thread across every subject area on the site.

Alongside the articles there is reference material designed to be copied directly into a project — extension methods, LINQ queries, JSON payloads, date and time handling with datetime pickers, PDF generation, and reusable CSS and Bootstrap layouts for landing pages. The reference sections are deliberately terse. Instead of a long theoretical preamble, you get a short explanation of what the snippet does, the code itself, and notes on where it commonly breaks. This makes the material handy for both quick lookups and deeper study when the behaviour needs clarifying.

For those who prefer to experiment rather than only read, the site offers an online C# editor where you can write and test code in the browser. It removes a familiar obstacle: setting up a project just to check a snippet's syntax or to see what a method returns. Because the editor sits alongside the tutorials, it can be used as a companion while following a walkthrough, letting you reproduce a sample, vary it and observe the difference in output before returning to the article for the next step.

Several of the most instructive posts are framed as community questions posted by working developers, answered and then discussed in the comments. Topics range widely — creating records through an API, sending notifications, building custom application components, working with entity references and triggers — but the underlying habit is the same: describe the symptom, narrow the cause, then propose a fix in code. That conversational format is approachable for newcomers while still giving experienced readers enough detail to disagree or improve on the original approach.

Beyond the code itself, the site covers the surrounding craft of building software for the web: design and layout with Bootstrap, responsive landing pages, Knockout and Angular component structure, and the object-oriented principles that keep a codebase maintainable once it outgrows a single page. Posts also touch on database design and query performance in SQL, because the majority of real bugs turn out to live at the boundary between layers rather than inside any one of them. This wider framing makes the library useful to readers who are not specialising in a single framework.

Regular readers are encouraged to follow the blog, browse by tag or archive, and subscribe to the feed so new material arrives where they already work. A comments and discussion area sits beneath most articles, allowing corrections and additions from other practitioners, and a forum-style enquiry path exists for questions that do not fit neatly into a tutorial. The intent is a living reference: articles age, frameworks shift, and the community keeps the older explanations honest by pointing out what has changed since publication.

The presentation deliberately favours legibility over decoration. A solid header bar carries the site identity and navigation, the content area sits on a plain white background, and an informational panel closes the page with standard notes on terms, privacy and policy. Body copy is set in a serif face with generous line height and paragraph spacing, which keeps long technical readings comfortable, while sans-serif type handles the header and site title. Sharp corners, thin borders and flat colour blocks give the whole thing an academic, document-like calm.

What ultimately holds the collection together is consistency of intent. Every article, reference note and answered question is aimed at a developer who has a problem in front of them right now and wants to understand it well enough to solve it independently. The tone is instructional without being condescending, the code is offered with context, and the framing stays focused on implementation rather than theory for its own sake. Whether the subject is lead conversion, a Lightning component, a REST call or a date picker, the aim is the same: to shorten the distance between a question and a working answer.

Topics

• .Net
• ASP.NET
• ASP.NET MVC
• C#
• Entity Framework
• Linq
• REST
• WCF
• Web API
• Windows Application
• Angular 2
• Angular JS
• Backbone JS
• Jquery
• JSON
• Knockout Js
• Node.Js
• CSS
• Bootstrap
• Database
• SQL Server

Looking for a specific answer? Start with the DWQA questions archive, or post your own question for other developers to answer.