[ Log In ]

v1.3.0 — April 2011

v1.2.5 — December 2010

v1.2.4 — August 2010

Support for the changes that MailChimp announced for their v1.2.6 and v.1.2.7

Deprecated methods removed; login() and getAffiliateInfo()

Bug Fixes & Tweaks

  • listAbuseReports() - was not passing the start & limit parameters when using Serial access.
  • campaignStats() - the default apikey was not assigned.
  • Api_BatchSubcribeError class renamedlistBatchSubscribeError for naming consistency.
  • Api_BatchUnsubcribeError class renamedlistBatchUnsubscribeError for naming consistency.
  • A few methods - Input class, removed explicit :base() in constructors - I had an idea at one point to use parms to the base class to control some functionality - since discarded.

Wrapper functional enhancements

Parameter assignment, default settings, etc., are now handled in the Parms class.
Customization should be done in the Input class to minimize impact of future wrapper enhancements.

First, there is an additional constructor in the Input class that takes a type of method Parms. A few new methods in the last release were implemented that way already; e.g., listsForEmail and chimpChatter .

Secondly, how you pass the parameters. If you passed parameters to the input class on your initial call to the constructor, that option is still the same, e.g.,

createFolderInput input = new createFolderInput ( apikey, foldername );

However, if you initially call the constructor with no parms, or only some of the parms, the subsequent parameter assignments are made to the input.parms.property, instead of input.property…

createFolderInput input = new createFolderInput ();

input.parms.apikey = apikey;

input.parms.name = foldername;

… or alternatively assign values to the Parms class and then pass that in…

createFolderParms parms = new createFolderParms ();

parms.apikey = apikey;

parms.name = foldername;

createFolderInput input = new createFolderInput ( parms );

What's changed - in the source
  • Input class is defined as "partial"
  • Input class contains a single property named 'parms' of type method Parms .
  • Input class provides the same multiple constructors, but they now update the 'parms' property via the Parms constructors, e.g., this .parms = new listAbuseReportsParms ( id, since );
  • Default settings logic moved from Input constructors to new Parms constructors.
  • Output classes have been changed to assign the Input 'parms' property directly to the inputParms property of the Output class, rather than loading individual values as was done previously, e.g., inputParms = input.parms;
  • Main 'execution' methods - parameters changed from input.property to input. parms.property
  • ValidateInput - parameters changed from input.property to input.parms.property

Additional wrapper properties and directives

api_UserData
api_CustomErrorMessages
api_xmlrpc_UseStringTag, api_xmlrpc_Indentation, api_xmlrpc_EnableCompression

Added settings to the XmlRpc request type to reduce the ContentLength and size of the request sent to MailChimp. These can be changed via the MCAPISettings; the defaults are:

  • UseStringTag = false ;
  • Indentation = 0;
  • EnableCompression = true ;

v1.2.3 — April 2010

  • Complete Codeplex issues 2271, 2355, 3397, 3610, & 3892.
  • Wrapper – Changes to MergeVar handling in various Methods & Types
  • Wrapper – Serial requests as POST form data.
  • UI — remove limitation on listBatchSubscribe() entry
  • See the detail change log for more info

v1.2.2 — January 2010

  • MailChimp Api v1.2.4 — All release changes supported
  • MailChimp Api v1.2.3 — All release changes supported
  • Geo‐location Segmentation options per MailChimp Api 2009‐Oct‐02 notices supported.
  • Wrapper — Cleanup of PerceptiveMCAPI.Types.Internal namespace and more consistent approach to complex return values from the Api (phase 1)
  • UI — allow selection of specific apikey to use for requests
  • UI — user control enhancements & clean‐up

v1.2.1 — October 2009

  • Support for MailChimp Api MCAPI v1.2.3 features
  • Wrapper — Configuration option for SecureAccess (https vs. http)
  • Wrapper — LINQ to XML replaces XmlDocument traversal for XML output types
  • UI — Show Api wrapper settings
  • UI — Implements user controls for input to improve ease of entry
  • UI — Implements user controls for output to improve result formatting
  • Wrapper & UI — Only serial requests populate the api_Request & api_Response fields. Formatting of XmlRpc request parameters for display has been removed from the wrapper, and moved to the UI in the form of the static class apiXmlRpcRequestDisplayFormat which formats the methodParms object for display in the UI.
  • Wrapper & UI — Code Refactor