MapForums
Community of VE/MapPoint Users and Developers
Microsoft's Weak Namespace
This is a discussion on Microsoft's Weak Namespace within the MapPoint 2006/2009 Discussion forums, part of the Map Forums category; I'll keep this rant short. When you import the MapPoint object model into a .NET project, you lose the ability ...
| |||||||
| Register | Blogs | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
06-16-2006
| |||
| |||
| Microsoft's Weak Namespace <Company>.<Context>.<Group>.<SubGroup>...... etc. For exmaple, custom generic controls are found in "MyCompany.Windows.Forms.Controls". This works because the fully qualified names of System.Windows and MyCompany.Windows are different. However in the case of MapPoint, there is no parent namespace. Thus, as soon as a name space called MapPoint is created (MyCompany.MapPoint), MapPoint can no longer be accessed. I'm new to .NET, interop and MapPoint. New jobs are great!         |
|
06-21-2006
| |||
| |||
|
Hi, Mappoint is a win32 application. And dotNet is (a the moment) a thin wrapper around win32 
__________________ rgds, Wilfried Mestdagh www.mestdagh.biz MapPoint coding demo Order MapPoint 2009 with Routing and User Tools Spreadsheet |
 |
| Tags |
| microsoft, namespace, weak |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
| ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Don't forget to add statement: using namespace MapPoint; | Anonymous | MP2K Magazine Articles | 0 | 05-12-2005 12:29 PM |
| With Microsoft's MapPoint Division, Location is Everything | Eric Frost | MP2K Magazine Articles | 4 | 04-14-2005 08:17 AM |
All times are GMT -5. The time now is 12:31 PM.
