using the Indexing Service with .Net

re: using the Indexing Service with .Net

Montaque — Thu, 22 Sep 2005 18:55:00 GMT

Hi guys,

I am using MSSEearch feature that incoperate with IIS. Problem is when I given criteria to search for C++ or C#, system is removing ++ and # from search criteria.

The criteria shown as header is showing as "C " or "VC " instead
of "C++" or "VC++". It is also highlighting the phrase "C" or "VC" instead of "C++" or "VC++", in the Query Result screen, which is wrong as to the search criteria.

Here is the example link for you: (though you cannot access but for reference)

http://192.168.2.4/null.htw?CiWebHitsFile=%2FTemp%2FBENE59591Resume%2Edoc&CiRestriction=%28%40CONTENTS+%28%22c++%22%29%29&CiBold=True&CiHiliteType=Full

output

"(@CONTENTS ("c "))" in

/Temp/BENE59591Resume.doc

....... text truncated .......

Amit

re: using the Indexing Service with .Net

Montaque — Fri, 27 May 2005 02:36:00 GMT

I strongly recommend to use IXSSO COM instead of OLE DB Provider, in particular if you expect big volume of indexing documents. The reason- OLE DB Provider doesn't support MaxRecords restriction/select top in SQL. IXSSO COM object allows to implement paging.

See the code that I am using on my post http://www.thespoke.net/MyBlog/MNF/MyBlog_Comments.aspx?ID=92495.

re: using the Indexing Service with .Net

TrackBack — Sat, 16 Apr 2005 07:39:00 GMT

^_~

Doubt: using the Indexing Service with .Net

Montaque — Fri, 25 Mar 2005 11:38:00 GMT

Is it possible to query a Indexing server on different machine from aspx page on different server? or is it possible to index directories on a network folder from the same machine as .net Application and use aspx to query indexing service.

Thanks

re: using the Indexing Service with .Net

Montaque — Tue, 01 Mar 2005 22:09:00 GMT

how can i create folder in index service from my program

re: using the Indexing Service with .Net

Montaque — Sat, 03 Jul 2004 05:27:00 GMT

Just passing through...

Couple of things to keep in mind:

OleDb provider is a couple of notches slower than the COM object query. I still prefer OleDb because of the flexibility and "commonality" with other providers.

There are no stored procedures with Index Server, it's an ISAM store like VFP or Jet. Views exist, but I think they are more trouble than they're worth since they don't appear to run any faster than "straight" SQL through the OleDb provider.