New Post: TwitterCredentials.CreateCredentials initialisation exception

Thanks for quick reply Linvi.

For completeness, I've noticed I now get this warning at build time:

1>  No way to resolve conflict between "Microsoft.Practices.Unity, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" and "Microsoft.Practices.Unity, Version=2.1.505.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35". Choosing "Microsoft.Practices.Unity, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" arbitrarily.
1>  Consider app.config remapping of assembly "Microsoft.Practices.Unity, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "2.1.505.0" [] to Version "3.0.0.0" [C:\Users\Craig\Documents\Visual Studio 2012\Projects\App\packages\Unity.3.0.1304.1\lib\Net45\Microsoft.Practices.Unity.dll] to solve conflict and get rid of warning.
1>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): warning MSB3247: Found conflicts between different versions of the same dependent assembly.

I was hoping nuget would manage all the dependencies etc. Have I inadvertently got the "wrong" Unity.dll included?