Try our conversational search powered by Generative AI!

NamespaceDoc.cs

Version InfoThis topic applies to Episerver.ConnectForMarketingAutomation 4.0.0 and lower. For later versions, see Sample Connector - IMarketingConnector

namespace DemoConnector
{
    /// <summary>
    /// The Episerver marketing automation interface (MAI) DemoConnector is a reference connector implementation
    /// that demonstates how to implement a working MAI connector that integrates with forms and visitor groups.
    /// <para></para>
    /// <para>There are two ways to create an MAI Connector:</para>
    /// <para>1. (a) Make a copy of the DemoConnector project, (b) open the project in visual studio, and
    /// (c) replace all instances of "DemoConnector" with the name of the connector you want to make. 
    /// (d) Additionally modify the NuGet spec and the post-build steps to name the nuget package appropriately.</para>
    /// <para>Note: This is probably the easiest way because the classes are already defined for you.
    /// </para>
    /// <para></para>
    /// <para>2.  (a) In visual studio, create a new class library project. (b) Add the Episerver and Marketing for Automation nuget packages, 
    /// (c) create the classes as needed starting with the <see cref="EPiServer.MarketingAutomationIntegration.Core.ProviderBase"/> and 
    /// <see cref="EPiServer.MarketingAutomationIntegration.Core.IProviderServices"/> classes.</para>
    /// <para></para>
    /// <para>Note: <see cref="EPiServer.MarketingAutomationIntegration.Core.IProviderServices"/>
    /// requires that a handful of other interfaces are implemented. It is OK for the implementations to throw NotImplementedException
    /// for methods for each class that is not supported by your connector.</para>
    /// </summary>    
    [System.Runtime.CompilerServices.CompilerGenerated]
    class NamespaceDoc
    {
    }
}

Related topics

Last updated: Dec 14, 2015