News

Intercept Studio 4.0 Monitors Code

Sleuth code errors. It may be near impossible to ship 100 percent clean code, but Intercept Studio 4.0 pledges to help .NET development teams come close.

It may be near impossible to ship 100 percent clean code, but Intercept Studio 4.0 pledges to help .NET development teams come close.

The product from Maryland-based AVIcode constantly monitors .NET applications for errors and performance issues in both development and production environments. The utility can isolate a specific line of problematic code, allowing companies to access "root cause" information. Intercept Studio tracks four types of events: security, connectivity, performance and code failure.

New features in version 4.0 include the ability to monitor code and collect data on non-networked computers. The new release also adds support for 64-bit applications built under .NET Framework 2.0. A Q1 service pack release will add out-of-box support for Windows Communication Foundation.

Managers can tune Intercept Studio to minimize performance impacts, says Marty Brandwin, AVIcode's vice president of marketing. "Event throttling lets people set rules that will only collect so many error reports of a given kind at one time. We don't want to become part of the problem."

AVIcode says Intercept Studio's low demands make it ideal for production environments. "In general, we're a single-digit CPU footprint," explains AVIcode Product Manager Chris Childers.

Forrester Research Application Development analyst Carey Schwaber sees products like Intercept Studio filling a growing niche. "It's not hard to leverage instrumentation when it's already in place, but it's hard to make sure that developers take the time to instrument their software appropriately in the first place."

Intercept Studio 4.0 starts at $12,000 for a single monitoring console and server agent.

About the Author

Chris Kanaracus is the news editor for Redmond Developer News.

comments powered by Disqus

Featured

  • Copilot Billing Shock Hits Developers

    Developer complaints about GitHub Copilot's new usage-based billing model have centered on unexpectedly rapid AI credit consumption, and neither GitHub nor Microsoft has responded directly to the backlash, though they have previously published guidance to lessen model usage costs.

  • Hands On with GitHub Copilot App Technical Preview: Turning a Blazor Issue into a PR

    GitHub's brand-new Copilot desktop app, in technical preview, handled a small Blazor issue from planning through pull request creation, but the hands-on test also showed why developers still need to verify agent work in the running app before merging.

  • At Build 2026, Microsoft Sets Up Windows as an OS for AI Agents

    Microsoft's Build 2026 Windows developer announcements point to a broader platform strategy for agentic AI, spanning terminal workflows, local models, app-building skills, Cloud PCs and operating system-level containment.

  • Slammed by Copilot Usage-Based Billing on Day 1, Facing $180 Bill for June

    A journalist using GitHub Copilot Pro details how a broken editorial workflow on day one of usage-based billing led to runaway token consumption, a projected $180 monthly bill, and practical tactics for cutting AI credit burn.

Subscribe on YouTube