I just updated to the latest version (august 18th, I had I think the Juli 5th version) and with it the typeconverters are not loading anymore. I can't select any typeconverters, so the project doesn't validate anymore. I haven't spend much time searching for a solution as the first thing I can think of is a bug in LLBLGen. Can I find the older builds somewhere so I can make shure it's the new build?

I just found the old version (July 23rd it was) on a backup. I coppied all the files in Solutions Design\LLBLGen Pro v3.0 back to my workstation. I opened the project again and now it validates fine. The content of the TypeConverters folder is in both places the same.

Did you compile the typeconverters in .net 4? If so, did you adjust the llblgenpro.exe.config by uncommenting the lines to make the designer run on .net 4?

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?

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.

Otis wrote:

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.

OK, thanks for looking into it.

In the next build, we'll include a specific small .exe for this: LLBLGenPro_NET40.exe. This small .exe is build against .net 4 and will enforce the designer to run on .net 4.0. We use the similar trick as with running the designer as 32bit app on a 64bit OS. We'll also add a section to the documentation illustrating this.

We decided not to add an installer thingy for this, because you might switch to .net 4 after you've installed plus writing the page for the installer was a cumbersome exercise, so we opted for this instead.