This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I'm trying to impliement a sql server full text search with lightspeed. I found your blog post on custom search and found that someone had linked a sample of a sql server full text search. http://sourceitsoftware.blogspot.com/2010/01/net-using-sql-server-full-text.html with the code being http://www.mindscape.co.nz/forums/Post.aspx?ThreadID=2702&PostID=8325 It all seemed fairly easy and so I used the code. I started a fresh project with one table and added in the custom search. The project errors as soon as it hits creating a lightspeed context. In vs debug the exception comes up as: An error occurred trying to create custom object with type name: [WebApplication1.SqlServerSearchEngine] on the aspx page the error is: Exception Details: System.ArgumentNullException: Value cannot be null. I've checked the namespaces and they are correct in the search setting in the lightspeed config in the web.config I don't even know where to begin to fix this. The search code seems straight forward and I can't see what's missing. Your lucene code works fine.
What am I missing?! |
|
|
I found that if I specify the search class in code on the context rather than the web.config it works. |
|
|
Your provider is obviously good because it works when you specify it from code, so the issue must be on the config file side. Are you using the fully qualified type name in the web.config (i.e. assembly-qualified, not just namespace-qualified)? |
|