 <p>I also got an exception saying "The invoked member is not supported in a dynamic assembly." and it caused me some headache to find its cause in my case.</p> <p>The reason mentioned in @StuffHappens' answer held also for me: I also had checked the "Thrown"-box for "Common Language Runtime Exceptions" in the Debug->Exceptions dialog. But, I also had unchecked Tools->Options->Debugging->"Enable Just My Code (Managed Only)". In fact, I didn't expect such exceptions to show up during degugging when I did so.</p> <p>In addition to the exception above, I also saw</p> <ul> <li>a MissingManifestResourceException from DevExpress complaining about some SkinInfoBlob.resources element not being present in a DLL containing a custom skin</li> <li>different FileNotFoundExceptions complaining about supposedly missing *.XmlSerializers assemblies having the same version as the assembly wherein a desired type resides (not only for our own assemblies, but also for NHibernate.XmlSerializers)</li> <li>a NotSupportedException from Spring.Net trying to resolve some object from NHibernate stating "The invoked member is not supported in a dynamic assembly." (or "Der aufgerufene Member wird in einer dynamischen Assembly nicht unterstützt." in german)</li> <li>a FormatException when dealing with TatukGIS symbols stating (or "Die Eingabezeichenfolge hat das falsche Format." in german)</li> </ul> <p>I checked "Enable Just My Code (Managed Only)" box again and all the mysterious exceptions vanished!</p> <p>I hope this may help someone to crawl out of this pitfall.</p>