This project is read-only.

MapWinGIS v4.9.2 released

Aug 26, 2014 at 8:05 PM
I've just released MapWinGIS v4.9.2.
This time we have a 32-Bit ( and a 64-Bit ( version.

It has a lot of new features like a raster calculator and a reclassify raster tool.
Here's a list of all new features:

Need some help getting started with MapWinGIS? Read this page:

Use it and let us know if you find any problems.


Aug 28, 2014 at 8:31 AM
Edited Aug 28, 2014 at 8:35 AM
I began to move a 4.8.8 soft to 4.9.2. Here are some problems encountered and possible solutions. I'll add what I'll find but it will be good to sum up others



Does Mapwingis plan to add a Legend component ? Is the only solution to recompile MawpinInterfaces as written here ?

Does AxMapWingis.AxMap move to MapWingis.Map ?

Does WinMap1_MouseMoveEvent(sender As Object, e As AxMapWinGIS._DMapEvents_MouseMoveEvent) Handles WinMap1.MouseMoveEvent

moves to

WinMap1_MouseMove(Button As Short, Shift As Short, x As Integer, y As Integer) Handles WinMap1.MouseMove ?

WinMap1.Leave event disappeared ?

WinMap1.Enter event disappeared ?
Aug 28, 2014 at 10:17 AM
Thanks Paul and all the people in the Team.

I've been using 4.9.0 with great results for 4 months, the meausirg cursor and the measuring logic,
the GMAPS layer, etc... for me was a great improvement over the 4.8.3.

Thanks again.
All the best.
Aug 29, 2014 at 7:45 AM
Thanks hellecaster. If you already like v4.9.0 you will definitely like v4.9.2, it has a huge improvement in Grid handling using a proxy image.
Could you write an article about how you use MapWinGIS? You can put it on your own blog or we can add it somewhere here on codeplex.
We really would like to know how the control is used.

olivier57: We have no plans for adding a legend component for MapWinGIS. We will have one for MapWindow v5, but that might take a while ;)
If somebody can solve the issues with the current version of MapWinInterfaces and send me the updated source code I can add the dll to the installer.
I'm not sure what you mean with
Does AxMapWingis.AxMap move to MapWingis.Map ?
You should just drop the map control on your form, that will create an object by default named 'axMap1'. Using Visual Studio you can make event handlers.


Sep 29, 2014 at 5:45 PM
Edited Sep 29, 2014 at 5:56 PM

I have some troubles trying to migrate an existing app to 4.9.2

If I just change references from 4.8.8 to 4.9.2,, VS 2010 is not able to open form, designer returning errors about Legend1 and WinMap1 components. So I began with copying project to another folder, then removed Winmap1 and Legend1 from the form, copied folder to another computer with 4.9.2. There I have no problem to open form, but I can't drop map control back on the form, as I get an error :

"Can't create Axhost component" 'System.Reflection.ReflectionTypeLoadExceptions" can't load required types". I tried to drop map control to a new project and form, and got no error. Of course this is not very useful for my migration...

By the way, I noticed that several useful (at least to me) functions disapeared
WinMap1.set_LayerVisible =>LayerDynamicVisibility ? (didn't find it in documentation)

Any help or suggestion would be appreciated


Sep 30, 2014 at 3:56 PM
Edited Sep 30, 2014 at 5:14 PM
I managed to achieve the migration. I can't tell exactly which steps I did and if all were appropriate but as a few ideas :
By the way, I managed also to recompile mapwininterfaces, setting it to 4.9.2 in assembly informations)
  • remove map and legend components
  • remove all references to mapwingis, interop, axmap...
  • remove all obj/bin folders from projects (containing old dll)
  • add 4.9.2 mapwingis.ocx to reference
  • add components in VS Toolbox add/browse (.COM for map, .NET for Legend)
  • drop components to form
  • rename winmap1 to axmap1 or something else...
About my previous post, I found that PointToClient, PointToScreen, set_layerVisible are there (but not found by Intellisense, neither in the documentation ?)
Marked as answer by pmeems on 10/3/2014 at 2:05 AM
Oct 3, 2014 at 10:05 AM
Thanks for your detailed description.
It will help others trying to migrate as well.

I will have a look at the hidden functions.


Oct 5, 2014 at 3:29 PM
set_LayerVisible is available in the documentation: and should also be in Intellisense.
PointToClient and PointToScreen are .NET control methods and exist in the .NET Framework. Here's a great explanation about these two methods:


Marked as answer by pmeems on 10/5/2014 at 7:29 AM