Thanks for the reality check John! A number of excellent intertwined questions as regards next steps given the pending shift from MapInfo Pro 7.x to the next generation of 8.X+.
My general understanding is that MapX as we now use and understand it will be replaced with a more extensive MapX.NET versioning? From this list, we know "someday soon" all of the MapInfo technology futures are designed to use the MapX.NET foundation; that MapX as we now know is to be replaced and likely not forward compatible? MapXtream.NET, if I can refer to it that way, to me seems an incremental step towards the eventual MapInfo Pro.NET 8.+ and its corresponding MapX.NET developers' engine? If these signals are more or less accurate, just how that will influence your pathway in the near term is uncertain; I too am confused. I would not expect that you will be able to get the same features from MapX.NET 6.+ as you will from the core technologies as expressed in MapInfo Professional.NET 8.+? Seems like that licensing model is long established in the current Pro Runtime licensing designs? In the shortrun, I would guess you/we may have several pathways. 1) Wait for the MapInfo Pro.Net 8.x and pay your upgrade costs. It has been revealed that legacy MapBasic code will still be supported and useful so we should have the best of both worlds? As for cost to jump to the next Pro version, well we can only go on what history has established as MapInfo policy? 2) Try to build on the MapXtream.NET version and its engine licensing costs with the goal of maintaining your code investment so it may be inserted into your upgrade MapInfo Pro.NET licenses. Or 3), continue with MapX 5 as a simple economic decision in the short run but knowing it will not be supported in the near future and the code legacy will need to be reworked (hopefully with as little pain as possible?). I am actually quite excited about the pending 8.0 version. We jumped from MapBasic to MapX many years ago. I will not even try to guess what sort of internal debates may have gone on within the One or the "Next" World View offices and would simply support the code-jockies by not freaking-out to get it wrong on time. But I would like to better understand these pending issues. MidNight Mapper Aka neil -----Original Message----- From: John Williams [mailto:[EMAIL PROTECTED] Sent: Saturday, July 10, 2004 2:09 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: MI-L MapX & MapXTreme 2004 .NET Hi List, I have a client that has existing investments in MapInfo Professional (in excess of 100 licences) and a corporate deployment of a MapX based application. An additional desktop solution is required that involves the development of departmental application similar to the existing corporate offering. With MapInfo's current products / developer tools I have narrowed my choice to two; MapX v5 or MapXtreme2004 NET. Each can be utilised as a component within either VB6 (for MapX) or Visual Studio .NET (for MapxTreme 2004 .NET), but I'm undecided which would be the recommended or preferred route forward. Clearly, there are pros and cons, but also significant issues with both. I am concerned about the vast difference in deployment costs, as the Map X SDK, runtimes and maintenance are approximately 50% cheaper than MapXTreme .NET., but also concerned about starting new development on a platform that maybe unsupported in the near future. I would greatly welcome any comments / feedback and assistance so I can confidently make proposals to my client, and equally importantly, the client has confidence in MapInfo as a long-term vendor that he wishes to commit to. Best regards John Williams JDW Consultant Services Ltd. UK Tel 07050 398200 UK Fax 07050 398100 International Tel +44 7768 895605 International Fax +44 8700 513376 Email [EMAIL PROTECTED] WWW www.jdwcs.com --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 12544
