We have a small CoreHost application targeting .NET 8 that works with Pro 3.4-3.6. To make it also work with Pro 3.7 we changed the .NET target to 10. We expect the new version to work with Pro 3.4-3.7 as .NET supports backward compatibility and Pro 3.7 can load add-ins targeting .NET 6-10. The application (as recommended) loads Pro assemblies from the Pro binaries folder.
After changing the .NET target, the application works OK with Pro 3.7 but throws an exception with Pro 3.4-3.6. The CoreHost assembly is loaded and initialized correctly but the exception is thrown when it calls the Geodatabase class constructor.
Any suggestions?
Thanks
Dejan
