.NET Tips and Tricks

Blog archive

Succeeding as a Tool Provider: Let Customers "Productize" the Tool

As part of reviewing dynaTrace's Enterprise and AJAX packages, I spoke with Eric Senunas, senior director of Marketing and Communications at dynaTrace, about the company's view of the .NET toolspace and the secrets to succeeding in that space.

dynaTrace is an interesting company to comment on the .NET toolspace because they've always supported both the Java and .NET environments. Eric said that they're seeing more non-.NET developers moving to .NET and a real, growing ecosystem around the Microsoft framework. As dynaTrace sees growth in the .NET area (Eric noted that 80 percent of their opportunities in Scandinavia are .NET-related), the company moves .NET features and enhancements "up in the roadmap." Eric's willing to ascribe that growth as much to Visual Basic 6 developers moving "into the enterprise" as developers moving from other environments.

What was more interesting from my point of view was Eric's comments about what it takes to succeed as a tool vendor. While dynaTrace has lots of good ideas developed in house, the company doesn't want to build anything that customers don't want. dynaTrace looks to its customers to help "productize" dynaTrace. dynaTrace's CEO is always asking where's the customer use case before agreeing to extending the product, said Senunas.

As a result, not all product enhancements are technical. For instance, with their latest release, one of the features that dynaTrace concentrated on was improving the customer's OOB (Out Of the Box) experience. dynaTrace is a very flexible tool with lots of customization options, coupled with the ability to create a variety of dashboards to view the information returned by dynaTrace. "We've never needed an army of consultants to get our customers up to speed", Eric noted, but customers did have to configure dynaTrace to do what they wanted before really using the product.

With the new release, in addition to numerous technical enhancements, dynaTrace provided Deployment FastPacks. These are pre-configured settings that set up dynaTrace to work with BizTalk, SharePoint and other environments where dynaTrace customers manage applications. Instead of having to take the time to tweak dynaTrace themselves, customers can get started using the product sooner.

The FastPacks also include prebuilt dashboards aimed at specific stakeholders within their customers: one dashboard provided information that operations people would need; a dashboard with more granular information targeted system architects; yet another dashboard was aimed at developers.

Posted by Peter Vogel on 04/21/2010 at 1:16 PM

comments powered by Disqus


  • Visual Studio Code Dev Team Cleans Up

    The Visual Studio Code development team focused on some housekeeping in the October update, closing more than 4,000 issues on GitHub, where the cross-platform, open-source editor lives.

  • ML.NET Model Builder Update Boosts Image Classification

    Microsoft announced an update to the Model Builder component of its ML.NET machine learning framework, boosting image classification and adding "try your model" functionality for predictions with sample input.

  • How to Do Naive Bayes with Numeric Data Using C#

    Dr. James McCaffrey of Microsoft Research uses a full code sample and screenshots to demonstrate how to create a naive Bayes classification system when the predictor values are numeric, using the C# language without any special code libraries.

  • Vortex

    Open Source 'Infrastructure-as-Code' SDK Adds .NET Core Support for Working with Azure

    Pulumi, known for its "Infrastructure-as-Code" cloud development tooling, has added support for .NET Core, letting .NET-centric developers use C#, F# and VB.NET to create, deploy, and manage Azure infrastructure.

  • .NET Framework Not Forgotten: Repair Tool Updated

    Even though Microsoft's development focus has shifted to the open-source, cross-platform .NET Core initiative -- with the aging, traditional, Windows-only .NET Framework relegated primarily to fixes and maintenance such as quality and reliability improvements -- the latter is still getting some other attention, as exemplified in a repair tool update.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events