![]() ![]() |
|
Open Client Developer's Guide | |
Search | Index | Glossary | |
|
![]() |
|
![]() |
![]() |
![]() |
Known IssuesPlease note the following known issues: Performance Impacts of Calling COM Objects from .NETCOM calls from .NET requires marshalling which impacts performance. Suggestion: minimize COM calls whenever possible. Combining Multiple COM CallsYou cannot combine multiple COM calls in a single .NET statement, like this: ComObj1.GetProp(ComObj2.getName()) This only occurs in some cases. Type-Casting IDM Generic ObjectYou cannot type-cast an IDM generic object into other IDM objects such as document, folder or store search object. MS has a fix and will include in the .NET service release. As a work-around, use the IFn.. Hidden interface of the object in the type-cast statement. For example: oGen = oLib.GetObject (…) oDoc = Ctype (oGen, IDMObjects.IFnDocumentDual) Performing Single Thread ADO SearchesWhen executing search using ADO, must set ASPCOMPAT = TRUE in aspx page. The rest of our IDM COM objects are running in STA (single thread model). In general, for STA objects you need to set the ASPCOMPAT flag and for MTA (multi thread model) objects you don't. Calls to JiGlueCalls to JiGlue cause the following known issues:
|
![]() |
|