I'm looking for ideas on how others work with the Vertical Mapper SDK. The dlls in the vm directory are not "findaable" by applications unless you put your MBXs in the vm directory. Doing this could eventually clutter up this directory, and also users with normal privileges usually cannot write to files in this tree (\Program Files\...) so you have to pay attention to where your MBXs write data.
If you put your MBX elswhere then you have to copy all the dlls that your program references to the same directory. I'm wondering if it wouldn't be such a bad idea to put the vm directory in the search path, but then I'll have to get users to learn how to do that if they want to run apps I've built. I also found that you have to have Vertical Mapper loaded if you use vm progress bars and want them to be visible. Calling vmInit() isn't enough by itself. I don't know if there are other issues like this, or if there's a simple function I need to call that's not in the manual. Anyway, I'd like to hear from anyone who's found a clean way to organize things to develop and deploy Vertical Mapper SDK apps. Once I get these to work, they're pretty slick, but it seems like there are a lot of arbitrary issues caused by file locations. - Bill Thoen _______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l
