I'm not concerned one way or another and realise trunk is still a work in progress. I just wanted to point out the clash between the same named variables/properties, I know C# is case sensitive and it isn't troubled by this, but vb.net is case-insensitive, and as it is currently, lucene.net will be unusable by any vb.net project where TopDocs is used.
David -----Original Message----- From: Nicholas Paldino [.NET/C# MVP] [mailto:casper...@caspershouse.com] Sent: Friday, 6 May 2011 11:41 a.m. To: lucene-net-dev@lucene.apache.org Subject: RE: [Lucene.Net] Minor problem with using code from the trunk with vb.net project. David, Apologies if this is pedantic, but that should be one of the goals, to move toward .NET naming conventions (which Lucene.NET does not abide by, and it makes for an odd fit). - Nick -----Original Message----- From: David Smith [mailto:dav...@nzcity.co.nz] Sent: Thursday, May 05, 2011 6:18 PM To: lucene-net-dev@lucene.apache.org Subject: [Lucene.Net] Minor problem with using code from the trunk with vb.net project. Morning, I checked out and compiled https://svn.apache.org/repos/asf/incubator/lucene.net/trunk yesterday, looking to update from 2.0.0.4 To get the library to work with VB.Net I found I had to edit TopDocs.cs (src/core/Search/TopDocs.cs). Being case-insensitive VB.Net can't differentiate between the three public variables (totalHits, scoreDocs & maxScore) and the three public properties (TotalHits, ScoreDocs & MaxScore) David
