Loupe - Log - Monitor - Resolve
Loupe / Developer's Guide / For .NET Framework / Third Party Integration / Using PostSharp with Loupe / Third Party Integration - Using PostSharp with Loupe - Deployment
In This Topic
    Third Party Integration - Using PostSharp with Loupe - Deployment
    In This Topic

    What Files do you Need?

    When you incorporate the Loupe Agent for PostSharp with your application you will need to distribute a few additional files with your application.

    File What is it? When would I use it?
    Gibraltar.Agent.PostSharp.3.0.NET40.dll The Loupe Agent for PostSharp 3.0 and .NET 4.0 This file should be distributed when your assembly targets the .NET 4.0 framework
    Gibraltar.Agent.PostSharp.3.0.NET40.xml Intellisense Help for the Loupe Agent for PostSharp This file is only used during development to provide Visual Studio with extended Intellisense help for the Agent API.  It never needs to be distributed.
    Gibraltar.Agent.PostSharp.3.0.NET45.dll The Loupe Agent for PostSharp 3.0 and .NET 4.5 This file should be distributed when your assembly targets the .NET 4.5 framework and later.
    Gibraltar.Agent.PostSharp.3.0.NET45.xml Intellisense Help for the Loupe Agent for PostSharp This file is only used during development to provide Visual Studio with extended Intellisense help for the Agent API.  It never needs to be distributed.
    PostSharp.dll The PostSharp public types library

    This file should always be distributed.

    PostSharp.xml Intellisense Help for PostSharp public types This fine is only used during development to provide Visual Studio with extended Intellisense help for the Agent API.  It never needs to be distributed.
    Because of the backwards compatibility built into PostSharp, the Loupe Agent for PostSharp 3.0 works with PostSharp 3.0 through 4.1.

    In addition, you will need to distribute the appropriate Loupe Agent files.  See Developer's Guide - Deployment for specific details.

    If you are using an automated deployment tool it will usually identify all of the necessary files because of .NET dependency tracking.

    See Also