Back to Downloads

MCAPI .Net Wrapper Change log


Below is a general overview of changes made to our MCAPI class over time. This is not meant to be a svn or cvs commit log, rather a straightforward description of the overall changes you will notice when working with our MCAPI wrapper as we make updates.
Be sure to check the API changelog for details on additions/changes inherent to anything using it.
2009-08-20 (Thu, 17 Aug 2009)
====================================================
* v1.1 of the API wrapper is now datacenter aware
* remove login() method from v1.1 of the API and require passing/using an API Key

2009-03-30 (Tue, 30 Jun 2009)
====================================================
* Fix campaignEmailStatsAimAll() so it actually works

2009-03-30 (Mon, 30 Mar 2009)
====================================================
* Fix to listBatchSubscribe() method to properly use tag for merge vars


2009-02-23 (Mon, 23 Feb 2009)
====================================================
* Add switch to support easily switching to HTTPS
* Make Timeout var easily accessible
* Make it easier to set the api key and skip the login method
* make MCCampaignContent support the "url" feature
* add missing methods:  campaignReplicate() , campaignDelete(), campaignEmailStatsAIMAll()
* start Strongly Naming & Signing/Keying the wrapper so it can be installed in the GAC (thanks to Brogdan Profir for the help)
* remove deprecated closeOneOhSecurityHole() method

2008-12-17 (Wed, 17 Dec 2008)
====================================================
* change merge vars to consistently use "tag" instead of "name" property b/c that made no sense


2008-08-26 (Tue, 26 Aug 2008)
====================================================
* released v1.1 of the wrapper to support v1.1 of the API 
* Significant changes to be aware of when upgrading to v1.1
    - The campaignCreate() method was completely overhauled and changed from the initial 1.0 
      version released. Read the docs on it before making the jump
    - API Keys were introduced. 
        - If you login() everytime and use the Key returned by login(), this will not affect you
        - If you have hardcoded the previous API Key returned, it will no longer work. We are 
          not backporting this and will not make old API Keys work with v.1.1
    - Error Codes/Messages were revamped. What you have now *should* work, but the recommended way
      now will be to check the numerical code we return and act on it
    - Return values now make more sense. Ints are ints when they shold be, etc.

------------------------------------------------------------------------
API 1.0 frozen, work on API 1.1 begins
------------------------------------------------------------------------

2008-06-04 (Wed, 4 Jun 2008)
====================================================
* v.1.0beta - Initial testing release to support v1.0 of the API, including support for all 
exposed methods.