PDA

View Full Version : Converting my Windows app. to ASP



BobFromBoston
10-12-2005, 03:01 PM
Hi,

My Windows application has MapPoint ActivreX tightly integrated to perform address lookups, travel times and distances, and to provide a map to the user, with the user's current information displayed. But I need to quickly develop an ASP version of my prorgram, and wonder if I will need to abandon MapPoint to make the tranisition.

The MapPoint webservice is not an option for me, due to the high cost per lookup. I operate in a very low margin business and do a lot of lookups, so even 1.6 cents per lookup breaks my cost model.

I have flexibility about the number of machines I'll be running. So does it make sense to have a dedicated Windows machine which uses the ActiveX control to provide my ASP program with addresss lookups and travel times lookups? That would fit nicely into my cost model since a slow machine can do 5-10 lookups per second. I could start with a slow machine and scale up as needed. Would this violate the license? It would be a single machine, yes, so in that sense would not violate the license. But it may be a violation, like trying to use a VCR to show a movie to a crowded movie theater. That's against the rules, and using a single Windows machine to process (for free) address lookups for a bunch of different location may be also a violation, but I hope to hear other people's opinions.

In addition to the issue of rights, how would I do it technically. I'm new to ASP, and wonder would I connect my ASP app. to the computer running MapPoint? Would I need to make a web service? Could I just map a drive and write the lookup results to a shared file?

And lastly, what about providing mapping via ASP? How might that work?

Thanks,
Bob

michele
10-12-2005, 04:04 PM
I think you have to pay one licence of MapPoint for everyone connects to your site.

So if you think your ASP application will be used by 40 different users, you have to pay 40 licences of MapPoint so the MapPoint Web Service could be a cheeper solution.

I created too a personal MapPoint webservice with .NET, the elaboration is performed by a Windows Service (yes I noticed that there are problems of multiple instances of MapPoint with Window Service so you have to use a Simple windows form application communicating with the Web Service for example via sockets).

I think you can have problems of DCOM authorization if you use MapPoint object directly by ASP pages (and maybe you have to check if you can run more then 5 instances of MapPoint at the same time).

You can read my topic about "MAPPOINT doesn't work as Window Service".

Michele

BobFromBoston
10-12-2005, 06:25 PM
Michele,

I'd love to read: "MAPPOINT doesn't work as Window Service", but can't seem to pull it up on the search. How should I search for it?


Bob

calv1ns
10-12-2005, 11:32 PM
Hey Bob

One way to find a post by a certain user is to click on their profile then click on "Find All Post by This User"

Good Luck,

oxcarz
10-13-2005, 08:02 PM
There are some technical issues using maPoint in asp.net. Asp net is initialized in a MTA apartment thread and Mapoint controls live in an STA thread. You can create an STA thread for the mappoint control and use a a container with a hWnd handle for the control. It might be easier to just use your windows forms application and just get requests and send maps out with tcp/ip. Just write a little servlet. Or even use filesystemwatcher and use a hard disk to exchange data.

The big issue with MS is always that EULA restriction about exposing any MapPoint controls to the internet.

BobFromBoston
10-14-2005, 05:23 PM
oxcarz,

There's a lot of information on your reply. Thanks. Very helpful.

But I wanted to ask about this, "The big issue with MS is always that EULA restriction about exposing any MapPoint controls to the internet."

Do you mean icons, like the little red car or the pushpin? What type of controls are you talking about.


Thanks,
Bob

oxcarz
10-15-2005, 12:04 PM
Hi Bob,

I think the intent of the EULA, besides encouraging you to use the MP webservice, is to prohibit exposing any maps to the internet. Static maps are OK, but "live" maps, routes, etc would be a no-no.

However, an asp.net application that serves maps on your LAN or intranet is fine.....u need a license for each browser that views the maps though.

Wilfried
10-17-2005, 12:43 PM
Hi,

There is also something for one thousand copies of the same map. I forgot what it reallly menth. Have to search agin in the agreement if you want.