I have written the following simple test in trying to learn Castle Windsor\'s Fluent Interface:
using NUnit.Framework;
using Castle.Windsor;
using System.Col
I got the same error after updating a referenced dll in a desktop executable project. The issue was as people here mentioned related an old reference and simple to fix but hasn’t been mentioned here, so I thought it might save other people’s time.
Anyway I updated dll A and got the error from another referenced dll let’s call it B here where dll A has a reference to dll B.
Updating dll B fixed the issue.