MapPoint Get MSAs Add-in

MapPoint Get MSAs Add-in

Learn how to create a MapPoint add-in by using the MapPoint object model and Microsoft Visual Basic .NET. With the add-in, users can query Pushpin sets to find out if any of the Pushpins are located within Metropolitan Statistical Areas (MSAs). The add-in then displays the query results in a Microsoft Excel workbook.

Read the full article here -
http://www.mp2kmag.com/a119--metropolitan.statistical.areas.msa.mappoint.html

To post a comment or question click on Post Reply.

Laura,

Thanks for the article. I've been wanting to do some MapPoint programing in .NET for a long time now. Reinforces that I am setting up the project correctly but what I can't figure out is how to enable debugging. I can create the program and run it just find but real time debugging (with breakpoints and such) don't work. I have created a MapPoint pluggin using .NET 2005 Beta and that seams to work fine. Do I have to wait for 2005 to get full capability?

Thanks,

Laura,

Thanks for the article. I've been wanting to do some MapPoint programing in .NET for a long time now. Reinforces that I am setting up the project correctly but what I can't figure out is how to enable debugging. I can create the program and run it just find but real time debugging (with breakpoints and such) don't work. I have created a MapPoint pluggin using .NET 2005 Beta and that seams to work fine. Do I have to wait for 2005 to get full capability?

Thanks,

Ok, I have finally discovered the source of this problem and posted the solution to my blog (http://hypercubed.blogspot.com/2005/04/visual-studio-cannot-debug-mappoint.html).

Apparently MapPoint would run all add-ins written in .NET using the latest version of the .NET runtime found on the machine. For my machines this was version 2.0. When trying to debug the application would crash because the debugger (apparently) was expecting 1.1. The solution is to force MapPoint to run the add-ins using version 1.1. To do this create a file in the MapPoint directory (the one containing MapPoint.exe) named MapPoint.exe.config. The file should contain the following text:

<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>
</startup>
</configuration>

After that I have no problems debugging .NET applications in visual studio 2003.

Very cool -- good work. Thanks for sharing. I've only been successful with .NET and MapPoint about half the times I've tried (would then just go back to VB6 or VBA), I'm sure I encountered this problem before and gave up.

Eric