TypeConverter can not be loaded. (BadImageFormatException): This might be caused by the fact it's been compiled with a newer version of the .NET framework. Type converters in this assembly will be unavailable

Posts   
 
    
Ole
User
Posts: 18
Joined: 17-May-2018
# Posted on: 01-Sep-2022 18:48:48   

Hi,

I am getting this error when opening my project in the designer V 5.3.1 .
Error loading potential type converter assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.3\TypeConverters\Flyware.TypeConverters.dll' (BadImageFormatException): This might be caused by the fact it's been compiled with a newer version of the .NET framework. Type converters in this assembly will be unavailable

I have upgraded the type converter project to .Net 4.7.1 from .Net 4.6.1 , but also tried to downgrade again to .Net 4.6.1 and I still get the same error.

What can be wrong ?.

Thanks

Attachments
Filename File size Added on Approval
BadImageEx.PNG 188,403 05-Sep-2022 12:18.16 Approved
Flyware.TypeConverters.zip 60,690 05-Sep-2022 12:33.54 Approved
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39160
Joined: 17-Aug-2003
# Posted on: 01-Sep-2022 19:12:51   

please attach the type converter (preferably with source) so we can check it. should be fine indeed, if you compile it against 4.7.1, I think windows update updates .net on windows to 4.8 nowadays

Frans Bouma | Lead developer LLBLGen Pro
Ole
User
Posts: 18
Joined: 17-May-2018
# Posted on: 05-Sep-2022 12:38:33   

I have added the files.

Further information.

I use the 32 bit version of LLBLGen.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39160
Joined: 17-Aug-2003
# Posted on: 05-Sep-2022 16:50:30   

I can't reproduce it. I built it from scratch, placed it in the typeconverters folder in the installation folder, ran the x86 exe and it loaded the dll just fine. Also the one you shippped.

Not sure what it can be on your system btw. If anything the debug target in your csproj doesn't have x86 as target platform specified, so if you run your typeconverter build as debug then it might go wrong in 32bit

Any explicit reason to still use the 32bit route btw? Just curious simple_smile

Frans Bouma | Lead developer LLBLGen Pro