Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Maybe possible solution for someone else: leaving out the .NET wrapper dll supplied by the vendor, and reference the underlying COM components directly form our project. This is described by Joe Parker in this thread: <a href="http://social.msdn.microsoft.com/Forums/zh-CN/vblanguage/thread/81c44b22-7bdc-4379-b0f6-953e1f96adfe" rel="nofollow">http://social.msdn.microsoft.com/Forums/zh-CN/vblanguage/thread/81c44b22-7bdc-4379-b0f6-953e1f96adfe</a>. "We were able to solve this with with MapObjects 2.3 by referencing the controls as COM components instead of using the .NET dlls that come with MapObjects. Remove the ESRI.??? references from your project, then add references to the COM component "ESRI MapObjects 2.3". This wraps the COM component with .NET code that will actually run in VS 2010. </p> <p>Then for the visual component, right-click in your toolbox and "Choose Items". Select "MapObjects 2.3 Map Control" from the "COM components" tab and then you will be able to add the control to a form. In my case I had to add it to a form then remove it just so Visual Studio would automatically add a reference to "AxMapObjects2" to the project. This reference has the visual control and some of it's supporting types. Then I just replaced our old AxMap references with AxMapObjects2.AxMap and other types with MapObjects2.Typename and everything worked (at least so far)."</p> <p>His method can be generalized I think to other similar situations too: "app&lt;->vendor .NET wrapper&lt;->vendor COM objects". Unfortunately the method may not be as easy in our case, because we not only have a COM control hosted in the app, but in other modules of our software we have export and import capabilities and other scattered stuff. So I cannot just reference the GUI COM component there, I only need some core functionality in those other places. But I thought I'll share this finding, it may help to others. I'm 100% sure that not MapObjects2 and our app will be the only victim. As more project will migrate to .NET 4.0 and still have some old legacy burden can face this.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload