Click here to Skip to main content
11,790,385 members (39,309 online)
Click here to Skip to main content

Considerations for implementing trace facilities in release builds of .NET applications

, 4 Nov 2002 98.9K 58
What is the best technique to produce trace output in release build of .NET application, i.e. when application is shipped to a customer or runs in a production environment? The article discusses pros and cons of standard .NET trace facilities, and presents some alternatives.


Members may post updates or alternatives to this current article in order to show different approaches or add new features.

No alternatives have been posted.


This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here


About the Author

Vagif Abilov
Architect Miles AS
Norway Norway
Vagif Abilov is a Russian/Norwegian software developer and architect working for Miles. He has more than twenty years of programming experience that includes various programming languages, currently using mostly C# and F#.

Vagif writes articles and speaks at user group sessions and conferences. He is a contributor and maintainer of several open source projects, including Simple.Data OData adapter, Simple.OData.Client and MongOData.

| | Privacy | Terms of Use | Mobile
Web03 | 2.8.1509028.1 | Last Updated 5 Nov 2002
Article Copyright 2002 by Vagif Abilov
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid