lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Currens (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENENET-167) Compact Framework & Silverlight Support
Date Tue, 13 Mar 2012 21:12:41 GMT


Christopher Currens commented on LUCENENET-167:

It's still on our list of things to do.  It will be very difficult to accomplish, and to be
frank, we don't have enough committers to pull it off at this point.  Lucene core (I don't
even want to look at the contrib) has 500 errors if you try to compile it using the Portable
Class Library tools in VS11 or the VS2010 extensions.  There's actually far more than that,
since VS tends to stop parsing files for certain errors.  Some of the things are easier than
others, for example, the Serializable attribute isn't supported in Silverlight, but we can
easily wrap that in a preprocessor conditional (*shudder*).  The more difficult things to
handle would be IClonable (it's used EVERYWHERE), the lack of HashSet<T>, everything
related to file system information, and other things.

If we had more committers, we could get this done quicker once we've done a bit of planning.
 It *will* eventually happen, as to when however, that's very much up in the air.
> Compact Framework & Silverlight Support
> ---------------------------------------
>                 Key: LUCENENET-167
>                 URL:
>             Project: Lucene.Net
>          Issue Type: Wish
>          Components: Lucene.Net Contrib, Lucene.Net Core, Lucene.Net Demo, Lucene.Net
>            Reporter: Andrew C. Smith
>            Priority: Minor
>              Labels: silverlight
> Lucene.Net should support the Compact Framework & Silverlight versions of the .NET
> I've looked into what it might take to do this and most of it is pretty trivial to be
able to support these frameworks. Most of what this would take is just changing the different
type of classes to use for collection classes used inside of Lucene.Net. 
> This does require changing some details in a lot of places, However this should *not*
bring any compatibility issues with *Java Lucene*'s API or index format. It will just change
the classes used to some different ones that the frameworks support and also maybe need 1
to 3 classes that might need to be implemented in itself.
> Having made these changes Lucene.Net can be more available to new devices such as running
on a window mobile cell phone, or your pda, or run in a Windows, Linux, or Mac computer that
runs a silverlight application. This will allow the .Net compact framework & silverlight
developers to use Lucene.Net in their applications to provide their users with the same capabilities
of an awesome search framework. Developers can also use Lucene.Net to provide them spell checking
capabilities in these environments. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message