Hi,

I'm not sure. I searched the programming help and I could not find anything of this feature in it.

Wilfred ...

My 2004 App seems to workly perfectly on my new 2006 client without any changes ... I did NOT install 2006 on my development machine ...

I am programming in VB.NET (VS 2003) ... I reference the 2004 Mappoint Interop dlls but do not register them, and I include the 2004 Mappoint .ocx and .dll in the executable path ... more than 10 forms use the Mappoint Control and the location object is called numerous times ... I always load Mappoint into the control using a template (.ptm) file created in 2004 ...

2006 seems to run a bit slower, but so far has not been a problem ...

Hi,

That is interesting news
Probably the way around will work also (using MP2006 ocx + dll's on a machine with MP2004 registered) sam way. It is word to test it.

Which *.dll 's do you include in execuable path ?

... Interop.MapPoint.dll ... version 1.0.0.0 ...
and
... MapPointControl.ocx ... version 11.0.18.1900 ...

are both placed in the executable path (the same directory as the executable) during installation ...

References in the program are to ...

... AXInterop.MapPoint.dll ... version 1.0.0.0 ...
and
... Interop.Mappoint.dll ... version 1.0.0.0 ...

Setup added as a detected dependency the MappointControl.ocx

Hi,

Those *.dll's are normal in the exe path, but not the *.ocx of course. I did the test, registered MP2004, did a rebuild, registered MP2006, copy the *.ocx version 2004 into the executable path.

Maybe I forgot something, or maybe it is different in C#. Will try again one of these days.

I can't imagine that the programming language would make this difference ... I would rather think that the fact that 2006 was never installed on my development machine has something to do with it ...

I have noticed that 2006 has MANY more registry entries that 2004 ...

--Jack

Hey guys,

I seem to be having the same problem, where I have recently upgraded from MP2004 to MP2006. Currently I have both installed on my dev computer and wish to compile my application for one or the other versions with as little code changing as possible.

Wilfried: How are you referencing MapPoint in your application, when using the batch file? I've tried a different method where you dig into the .vbproj file and edit the references from there, but learned that the GUIDs for each library are stored there. So even though you register the desired version of MP, how does that change the references within VS to the correct library?

Thanks in advance!

Hi,

I had to search for that because by default VS copy it all in the project folder. I almost discoverd it by accident how to do

If you right click the project, then 'Add' then 'Existing item', after selecting it dont click OK, but near the button is a little arrow. Clicking it brings up a popup menu and you can click 'Add as link'. Then it is not copied and the version class can be used by all projects.

Maybe there are other approach as well. Maybe I need to RTFM