I’m working on a vb.net project and I’m getting a compiler error because of the lucene.net library.
There are properties as follows
[Obsolete] // Please use TotalHits instead
totalHits
TotalHits
Now the issue is that vb.net is case insensitive in this regard, so it’s recognizing both properties and not allowing my to build the project.
Is there a way to circumvent this issue without recompiling the code myself and removing the obsolete properties?
Sorry about that! If it’s any consolation, it is something that we’re working on. CLS Compliance, where fixing naming is top priority for VB.NET support, is targeted for the next release, Lucene.NET 3.0.3. The current code (unreleased) can be found here. Those properties are from the
TopDocsclass, and I specifically remember making that change already. However, since it’s not an official release, you would have to compile it yourself (which from your question, seems like something you’d rather not do). I find the personally find the branch to be very stable, though, and there’s been a lot of changes to greatly improve performance, including support of generics.We’ve just released 2.9.4 and 2.9.4g, and are about to merge the 3.0.3 branch into trunk. Not all of the Name ambiguities have been fixed however, though I think the most annoying ones have. Keep in mind that other methods that were previously marked
[Obsolete]may have also been removed. If you want to follow progress on the release of 3.0.3, you can keep checking back to our website. The specific issue for CLS Compliance is here, so you can also track the progress on it there.I’m hoping that we can release the new version very soon and add official support for other .NET languages.