El wrote:
Of course, the LLBLGenPro.exe.config is overwritten . That solved it. Thanks!
Isn't it an idea to notify the user that x typeconverter assembly could not be loaded for x reason?
Unfortunately, it simply does a reflection of types which derive from a given type X, so if you compiled it against .net 4, the assembly won't even load but it doesn't know at that point whether that assembly was the one which contained type converters in a loaded project.
We could indeed show an error (I think we do issue a warning, have to check) when the project is loaded and type converters couldn't be loaded, but why they couldn't be loaded is unknown. (so the quest to find why is the same).
We'll look into making running the designer under .net 4 a bit easier, as re-installing an update is now a bit of a pain. (not the installer, but the config changes which are necessary every time.