When you tag methods with aspects PostSharp inserts itself in the build process to post-process compiled assemblies adding code at the MSIL level incorporating the aspect with your code.  Each time you build your project the aspect code is inserted in the right places.  With this approach you don't have to worry about autogenerated code getting in the way of your ability to maintain and work with your application. 

For example, in the code snippet below, the SearchGoogle method is tagged with the GTrace aspect. This would result in Loupe logging every call to this method including arguments, return value and execution time. Alternately, if [GTrace] were applied to the the SearchWrapper class, calls to all methods in the class would be logged.

public class SearchWrapper
{
    [GTrace]
    public Results SearchGoogle(string search)
    {
        // ...
    }
    public Results SearchBing(string search)
    {
        // ...
    }
}

Aspects can also be assigned to whole assemblies with flexible filtering so that you can instrument whole programs with just a few attribute tags.  For more details, see PostSharp Tips & Tricks.

For ideas on how to effectively use Loupe and PostSharp together see Using PostSharp with Loupe - Best Practices.

The Loupe Agent for PostSharp contains a set of PostSharp aspects that integrate with Loupe.  These aspects make it easy to add as much or as little code instrumentation as needed to debug and support your application during testing and production quickly and easily.

For ideas on how to use these different aspects in combination see Third Party Integration - Using PostSharp with Loupe - Best Practices. 

Third Party Integration

Developer's Guide

PostSharp