I think we should stick to .NET 2.0 till Lucene 3.0 which can be a good place to switch to .NET 3.5 (so will Lucene.Java do also).
There are also a lot of places where smarter codes can be used ( replacing "GetEnumerator+while" with "foreach", implementing a .NET like "Set" instead of using Hashtable etc.) But it can be a problem in porting unless we catch up with Lucene.Java. DIGY -----Original Message----- From: Michael Garski [mailto:mgar...@myspace-inc.com] Sent: Monday, November 09, 2009 7:26 PM To: lucene-net-...@incubator.apache.org; lucene-net-user@incubator.apache.org Subject: 2.9 Target Framework Apologies for the cross-posting to both lists, but I think this issue is applicable to both. What is the target framework for Lucene.Net 2.9? I'm assuming 2.0 but would like to ensure this is defined. There are a few cases in some of the internal implementation where use of LINQ would be handy, such as in collection transformations to arrays. Overall, it's not a big deal to target 2.0 however some of the implementation will be a bit more elegant and precise if we target 3.5. Cheers, Michael Michael Garski Sr. Search Architect 310.969.7435 (office) 310.251.6355 (mobile) www.myspace.com/michaelgarski
