<div>
You could interface with Google and let them do the searching for you.<br />
<br />
Just allow the pages to be searchable and then invoke your own web service from them.
</div>


You could interface with Google and let them do the searching for you.

Just allow the pages to be searchable and then invoke your own web service from them.

<div>
the data is not meant to be public, however.
</div>


the data is not meant to be public, however.

<div>
<div class="content wysiwyg-content">
I want to allow users to specify profiles (previous history, interests...) &nbsp;and then have this information be searchable. &nbsp;The most common search would be something like this:<br />
<br />
I'm looking for a person who is interesting in computer programming, looking for a job, and willing to receive job information. &nbsp;<br />
<br />
Many of the fields could be specifically enumerated. &nbsp;For example, there may only be 10 different types things one can be &quot;willing to receive&quot; or the topics could be specific. &nbsp;However, there may be some free form text as well. &nbsp;<br />
<br />
I can choose the persistence store (xml files or database or both), the indexing method, and the search engine. &nbsp;I would venture to guess that this sort of thing is pretty standard practice, so do people have suggestions as to how to do this the best/easiest way? &nbsp;<br />
<br />
the front end will be ASP.NET pages or a remoting client or both. &nbsp;
</div>
</div>


I want to allow users to specify profiles (previous history, interests...)  and then have this information be searchable.  The most common search would be something like this:

I'm looking for a person who is interesting in computer programming, looking for a job, and willing to receive job information.  

Many of the fields could be specifically enumerated.  For example, there may only be 10 different types things one can be "willing to receive" or the topics could be specific.  However, there may be some free form text as well.  

I can choose the persistence store (xml files or database or both), the indexing method, and the search engine.  I would venture to guess that this sort of thing is pretty standard practice, so do people have suggestions as to how to do this the best/easiest way?  

the front end will be ASP.NET pages or a remoting client or both.  

Advice for implementing Search Engine

C# is an object-oriented programming language created in conjunction with Microsoft’s .NET framework. Compilation is usually done into the Microsoft Intermediate Language (MSIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR).