lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lucas" ...@toddlucas.net>
Subject RE: Metro port of Lucene.net
Date Wed, 30 May 2012 17:27:16 GMT
If you look at MSDN, the new WinRT (Windows Runtime) is designated "Metro
style apps".

There are indeed significant changes. Most of it relates to the asynchronous
nature of the runtime and the sandboxed IO libraries. I understand that a
wrapper has been written for SQLite, so it's possible. I don't know what
degree of effort would be required, though. My guess is that any port will
be a subset of the full Lucene.NET set of projects.

To do the port, you must run on Windows 8 and you need to build with Visual
Studio 11. The .NET 4.5 runtime and C# compiler have new support for the
async/await keyword pair and you need to build on Windows 8 to target WinRT.

-----Original Message-----
From: Christopher Currens [mailto:currens.chris@gmail.com] 
Sent: Wednesday, May 30, 2012 9:51 AM
To: lucene-net-dev@lucene.apache.org
Subject: Re: Metro port of Lucene.net

To clarify, that list is not everything missing from .NET for Metro, but
rather the types in the 637 errors I found trying to compile lucene.

On Wed, May 30, 2012 at 9:50 AM, Christopher Currens <
currens.chris@gmail.com> wrote:

> This MSDN page has some good information on it:
>
http://msdn.microsoft.com/en-us/library/windows/apps/br230302(v=vs.110).aspx
,
> though it's comprehensive, and not concise.  This here:
>
http://msdn.microsoft.com/en-us/library/windows/apps/br230232(v=vs.110).aspx
> is a listing of all the available namespaces and types (many are missing
or
> added).  I know that if you're using VS11, you can create a Portable Class
> Library to target different frameworks (much like the plans
> in LUCENENET-167 and LUCENENET-411).  If you selected the .NET for Metro
> Style Apps alone, I currently get 637 errors.
>
> Here are the main classes/namespaces missing:
>
> -- System.SerializableAttribute
> -- System.NonSerializedAttribute
> -- System.ApplicationException
> -- System.Collection.ArrayList
> -- System.Converter
> -- System.Security.Cryptography
> -- System.IO.DirectoryInfo
> -- System.IO.FileInfo
> -- System.IO.FileAccess
> -- System.IO.FileStream
> -- System.Collections.Hashtable
> -- System.IClonable
> -- System.STAThreadAttribute
> -- System.SystemException
> -- System.Threading.ThreadPriority
> -- System.Threading.ThreadStart
>
> These are some hefty changes.  The largest change is the loss of the
> serializable attribute.  I'm actually not terribly familiar with the PCL,
> so I'm not sure if there's a conditional way to include things, or if
> preprocessor commands would be necessary.
>
>
> Thanks,
> Christopher
>
> --
>
>
> On Wed, May 30, 2012 at 8:36 AM, Prescott Nasser
<geobmx540@hotmail.com>wrote:
>
>>
>> Does anyone have a good reference for the limitations this will have?
>> What libraries won't be accessible, etc?
>>
>> > From: geobmx540@hotmail.com
>> > To: lucene-net-dev@lucene.apache.org
>> > Subject: RE: Metro port of Lucene.net
>> > Date: Wed, 30 May 2012 08:34:05 -0700
>> >
>> >
>> > I haven't taken too much time to look into the limitations, but this
>> should definitely be on the list of things to do.
>> >
>> > > Date: Tue, 29 May 2012 21:18:33 -0700
>> > > Subject: Metro port of Lucene.net
>> > > From: arun@kno.com
>> > > To: lucene-net-dev@lucene.apache.org
>> > >
>> > > Wonder if there are plans to port Lucene.NET to the restricted Metro
>> .NET
>> > > libraries ?
>> > >
>> > > Thanks
>> > > Arun
>> >
>>
>>
>
>


Mime
View raw message