Hi,
I have a layer that has been assigned a GdalProjectionConverter. When trying to serialize the layer to file, I get a serialization error. How should this be treated?
Regards,
Damian
Hi,
I have a layer that has been assigned a GdalProjectionConverter. When trying to serialize the layer to file, I get a serialization error. How should this be treated?
Regards,
Damian
GdalProjectionConverter is not marked as Serializable because some of its internal fields are not serializable. What serialization methods are you using? We’ll see if there’s some way we can work it around?
Using normal GeoSerializer.
Regards,
Damian
Just fixed it and created a new version for you, pull the latest (ThinkGeo.Gdal 14.4.0-beta087 ) and have another try.
Hi Ben,
I loaded beta 088 because of the dragdrop issue. I still get the serialization error on the projection converter.
Regards,
Damian
ThinkGeo.UI.Winforms beta088 goes with ThinkGeo.Gdal 14.4.0-beta086, you need to upgrade to ThinkGeo.UI.Winforms beta089 which goes with ThinkGeo.Gdal 14.4.0-beta087
Hi Ben,
Okay, that works.
If I had just loaded Gdal beta 087 would it automatically grab UI 089? Just trying to figure out your system… since the two version numbers don’t align, it is pretty confusing what is needed with what.
Should I update anything else?
Another thing is that once I updated Gdal beta 087 I get the following reference exception. The problem is that the library is loaded. I have deleted bin and obj and it still persists. Oddly enough the project builds and runs.
The type ‘Canvas’ is defined in an assembly that is not referenced. You must add a reference to assembly ‘PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.
Regards,
Damian
Hi Damian,
Beta versions aren’t lock-stepped, so updating GDAL87 won’t auto-pull UI89. This is why we always recommend to upgrade to the latest beta together to avoid mismatches. The stable release will share the same version.
Regarding the exception, I would suggest restarting VS or even your computer, restarting just solves lots of Microsoft issues.
Thanks,
Ben