More in this section
Forums / Developing with Sitefinity / COM interface to search engine

COM interface to search engine

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
2 posts, 0 answered
  1. Dave
    Dave avatar
    29 posts
    31 Oct 2011
    21 Dec 2011
    Link to this post
    I am in the process of integrating Sitefinity into an existing site that is a combination of ASP.NET and classic ASP.
    Is there any COM interface to Sitefinity's search engine that I may use from the ASP code? We're currently using the Windows Content Indexing Service, but I'd like to keep a single search mechanism in place for Sitefinity and the ASP stuff.
  2. Peter
    Peter avatar
    36 posts
    30 Jun 2017
    23 Dec 2011
    Link to this post

    Thank you for your question and the nice words for the new Sitefinity 4.4. I am glad that you appreciate the new features that our last release come shipped with.

    The assemblies which come shipped with Sitefinity, including those of Lucene.NET (Telerik.Sitefinity.Utilities.Lucene.Net), are market with [assembly: ComVisible(false)].  As a consequence all public types within the assemblies are not visible to COM clients.

    Of course, you have the fully exposed API of Sitefinity, with which you can interact within the scope of you Sitefinity solution. Thus, your suggestion for a wrapper makes a perfect sense and you could create a wrapper project that has COM interface capabilities to serve your needs.

    Another thing devoted to this very topic is that in Sitefinity no class members  are set to ComVisible(false) -  only on the class level. So for example, if  ClassA is with ComVisible(false) attribute, the class and its members are invisible to COM. However, if you derive ClassB from ClassA and export ClassB to COM, ClassA members become visible base class members of ClassB. So, please have that in the back of your mind as it may be useful to you. Please, also check this Microsoft Guidelines for exposing .NET types to COM in case you feel you need to make some research on the topic.

    If you need any assistance from us, please let us know.

    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
2 posts, 0 answered