MapForums

I'm developing a VB.NET application that use the MappointControl included in Mappoint2004. I will supply the application to a customer without the software Mappoint2004. The customer will buy and install its own copy of Mappoint.
What does it happen if he installs Mappoint2006 (or 2009) instead ?
Everything should works ?
The point is that I have a regular license of Mappoint 2004. I would avoid to buy a 2006 version just to develope the application, I'm not interested to have a 2006 license. But the customer probably will buy a 2006 or 2009 version to benefit of updated maps.
Marco

Hi,

For the object model it works with all versions. But if you use the activeX control you have to install MP2006 and recompile. I don't know for the 2009 version.

__________________
rgds, Wilfried Mestdagh
www.mestdagh.biz
MapPoint coding demo
Order MapPoint 2009 with Routing and User Tools Spreadsheet

What Wilfried says is correct, but depending on how you built your .NET assembly it might reference a specific version. This probably won't work until you change the reference to point to the later version (Wilfried: correct me if I'm wrong, you have more .NET and MP experience...)

As for the actual interface MP2006 adds some relatively minor things - doesn't remove anything. We expect MP2009 to do the same.


Richard

__________________
Winwaed Software Technology LLC
http://www.winwaed.com
See http://www.mapping-tools.com for MapPoint Tools
Pre-Order MapPoint 2009 today: http://www.mapping-tools.com/mappoint2009

Hi, thank you.
I have a little experience in this and I don't understand well the difference from Object model and ocx. ....
I have declared in my vb.net application the reference to MappointControl, then I have placed the control on the form, then I use the various method to find a location, to add a pushpin, etc.
I think I'm using the OCX, right ?
So if I install this application (created using the mappoint control of 2004 version) on a PC where is installed Mappoint2006 it will not works ?
Marco

Hi,

Correct.

Correct, this is my experience.

__________________
rgds, Wilfried Mestdagh
www.mestdagh.biz
MapPoint coding demo
Order MapPoint 2009 with Routing and User Tools Spreadsheet

uhmm .... I don't want to buy a license of Mappoint2006 because I don't really use it. Just to put me in peace with a license, I have bought now for a few price a Mappoint2004, but now it seems it is not useful because sure the customer will install 2006 ...

Is there any solutions ? For example, is it possible to dinamically load the proper Mappointcontrol according on wich version of Mappoint the customer install ?
I mean, I don't include the control in my application. When it runs, it looks for a Mappoint (2004/2006/2009) installed on the pc, then automatically load the relative Mappointcontrol (which ?) , place it on the form and show the map ?
Marco

I don't know about the control, but with VB/VBA Automation (examples at Working With Excel and MapPoint - MP2K Magazine ) you can definitely be version independent.. you just don't specify the version number in the code.

I don't really know, but I suspect with the control when you drop it in it IS version specific..

Eric

__________________

Yes, but It seems to me that a control can also be dinamically created in a form in runtime, not only dropped in a form at design time.
I feel that some solution is around me but I don't know how to proceed.
Marco

In the world of COM (eg. C++ and VB6) you don't necessarily have to specify the version at compile time - and it should work with the version you develop against and later versions.
I assume it is the same with the OCX - this is only particular way of using the COM interface.

The standard way in the .NET world is to reference a specific version - so it will only work with that version. This is a problem I have with MPSuperShape - I will probably have to release a MapPoint 2009 version.

The way around it with .NET using the standard object model, is to use late binding. I think this probably should work with the OCX? (my understanding is that it won't work with add-ins).

I've promised Eric an article on MapPoint and late binding, but it will be using C#.


Richard

__________________
Winwaed Software Technology LLC
http://www.winwaed.com
See http://www.mapping-tools.com for MapPoint Tools
Pre-Order MapPoint 2009 today: http://www.mapping-tools.com/mappoint2009

It is a bit difficult for me to understand this concept.
But:
isn't it possible to do something like this (I just copy and paste an example to give the idea)

Dim myControl1 As MyControl = CType(LoadControl("TempControl_Samples1.vb.ascx"), MyControl)
Controls.Add(myControl1)

What I'm thinking is (during runtime) to see which version of Mappoint is installed on the PC, then load the proper control and place in the form.

Doesn't it works ?
Marco