it's not about whether you have binding or not. type load exceptions might come in for various reasons. IMHO Episerver forms code should also respect settings on episerver.framework element and look for types that are excluded (it just does this `AppDomain.CurrentDomain.GetAssemblies()`).
IMHO these errors can be ignored until the moment when you see your own assembly there that contains Episerver forms components that should participate in application logic..
I filed a bug regarding this and hopefully Form team will fix it in future. I would recommend to reach out for developer support service for further assistance
The errors can be ignored.
EPiServer.Forms basically just gets all assemblies in current domain and then get all types from each domain.
ReflectionTypeLoadException is thrown when any classes of modules can not be loaded. Because assemblies can be loaded dynamically (e.g load all assemblies in a folder) and sometimes it fails to load. Fortunately, when it fails to load, the Exception still contains the information we need.
For more infor, check out this post or StackOverFlow answer
still IMHO forms should respect episerver assembly scanning rules and check for the assemblies that are allowed to scan. this will also help to avoid perfomrance implications that we are seeing :) we do have ~ 200 .dll in bin. hahahaa I know - there is something wrong with my bin directory.
I am seeing the following error repeated quite often in my log files in all our environments.
The first occurance I can find of this exception being logged is when we switch to Azure AD login.
Does anyone know if this is a problem that needs solving or that I can ignore?
The assemblyBinding is included in our web.config
I have no idea if the error that is getting logged is related to a phenomenon we are seeing when using edit mode, but we are experiencing blank screens in edit mode, after we switched to Azure AD.
The blank screen problem occurs mostly in Chrome and can be solved by refreshing or resizing the window.
If I open the development console in Chrome, it do not see any errors.