
Dealing with Mailchimp.Net gotchas
Dealing with the Mailchimp API and Mailchimp.Net and some of the gotcha's you may come across
With over 20 years of experience in corporate and agency .Net web development, Digbyswift can meet and support your requirements. We specialise in Azure, Umbraco CMS solutions.

Tag list:
MailchimpJSONSerializationIntegrationsConfigurationUmbracoAsyncTortoiseSVNSource ControlVisual StudioWorkflow FoundationNode.jsGruntJavascriptSQLLoggingElmahLog4netException handlingWebDeployIISDeploymentsAirbrakeUnit testsSam KitsonWix
Dealing with the Mailchimp API and Mailchimp.Net and some of the gotcha's you may come across

Custom controllers in Umbraco natively support async/await operations but it's not clear how to implement an asynchronous controller correctly.

We wanted to create a patch containing all the updated files but with the folder structure of our website. This way we could simply FTP the patch up to our website without having to upload any additional files. We’d love to know if there was a better or simpler method but this is what we did.

By default your Backoffice would be accessible at /umbraco. This not only provides users an opportunity to (try and) access the Backoffice but it also divulges the fact that you are using Umbraco and .Net and it may be possible to exploit this - neither Umbraco nor .Net are flawless.

How to fix the "Microsoft.Build.Tasks.Xaml.PartialClass GenerationTask task could not be loaded from the assembly Could not load file or assembly XamlBuildTask.dll or one of its dependencies" build error

We recently inherited a project with a Grunt-based Javascript boilerplate that would not install, falling over installing node-sass. It would throw an error stating that Python2.7 was missing and also that the C++ MSBuild task could not be found. Why?!

So you’d like more consistency in your database? Try SQL User-Defined Types (UDT). The concept is simple. You essentially create a new, custom type based upon an existing type but with predefined properties.

There are many ways to upset a user and moving the user to a new “Whoops, we did something wrong!” page would certainly upset the user.

Setting up WebDeploy on a server is never as simple as it should be because there are several places it can go wrong and there is a reliance on things being done in the correct order. We explain how to get it right each time.