ThinkGeo.com    |     Documentation    |     Premium Support

Error when migrating project framework 4.7 to core 3.1

#1

Hi,

Currently our tools run on the 4.7.1 framework and we are using the Thinkgeo 10.6.21 version.
We will migrate our platform to core version 3.1
The first step we do is to migrate the core projects. The nuget packages remain in Framework 4.7.
For all the packages that we use, we have no difficulties except for the Thinkgeo package.
We have this error below :
Error MC1000: Erreur de build inconnue, ‘Could not find assembly ‘ThinkGeo.MapSuite, Version=10.0.0.0, Culture=neutral, PublicKeyToken=0828af5241fb4207’. Either explicitly load this assembly using a method such as LoadFromAssemblyPath() or use a MetadataAssemblyResolver that returns a valid assembly.’ (1, 1)

How do we get Thinkgeo to work in our configuration?
Do you have an example?

Thanks a lot.
Regards.
Steph.

#2

Thanks Steph,
The mapsuite v10 does not support the .Net core. You need upgrade to the mapsuite V12 first. Here is the upgrade guide.
https://wiki.thinkgeo.com/wiki/thinkgeo_12_upgrade_guide

Thanks

Frank

#3

Hi Franck,

Thanks for your answer.

I still have few questions.

  1. If we switch to core, are all the features that are present in the Framework version present in the core version ?
    We use the following features in our application (differents types of layer)

inMemoryLayer
SqlLayer
GoogleMapLayer
BingMapLayer
OpenstreetMapLayer
WmsLayer
WMtsLayer
On-the-fly reprojection vector layer
ShapeLayer
KmlLayer
MultiGeoRasterLayer => Display rasters with format tif / ecw /jpeg2
Style point or line or polygon
Core version works on x32 and x64 machines ? How deploy ? …

Formulated differently, does the core version cover all the functionality of the framework version ?

  1. For the license, if we have a Thinkgeo Wpf Framework license, can we use the core version ?
    Or is this a new license?

Thanks

Regards.

Steph

#4

Thanks Steph,

  1. Mapsuite V12 support both .Net framework and .Net core. .Net framework and .Net core has the same features in V12.You can find the how do I sample for mapsuite V12 here. https://gitlab.com/thinkgeo/public/thinkgeo-desktop-maps/-/tree/master/samples/winforms/HowDoISample
  2. Right now the KmlLayer not support in V12. But we are working on it.
  3. If you have mapsuite wpf V10 license. You don’t need the new license for the wpf V12. You can active the WPF V12 with the same credential as V10.

Thanks

Frank

#5

Hi Franck,

Thanks for your answer.
I have few more questions.

For example, my project is migrated to.net core 3.1 (cf. screen shot)

NugetPackageitre
NugetPackageitre986×408 62.2 KB

I am trying to migrate the thinkgeo package to V12 and the version does not appear in the nuget packages.
How do I see version 12 appear, please?

Is it possible with ONE thinkgeo Wpf license to be able to deploy projects which have not yet been migrated and which will remain for a while in V10, and other projects migrated in Version V12?
As we have a lot of projects, we will gradually migrate to .Net core.

Thanks.
Regards.

Steph

#6

Thanks Steph,
1. The nuget package name changed. You can search by “ThinkGeo.UI” in the nuget manage page.
https://www.nuget.org/packages/ThinkGeo.UI.Wpf/13.0.0-beta165
Here is update guide.
https://docs.thinkgeo.com/products/desktop-maps/v12.0/upgrade-guide/

  1. Yes. The target machine could run both on V12 and V10 application. But you need generate the runtime license for each application by the product center tool(V10 or V12). Your developer license(Mapsuite wpf editon) could generate both V10 and V12 wpf runtime license.

Thanks

Frank