2011 6:30 PM
To: lucene-net-dev@lucene.apache.org
Subject: Re: [Lucene.Net] Could not load assembly
> If thats the case, I'd propose exploring the portable class library project
> for the long run.
>
> Its supposed to constrain you to the shared APIs that are available in the
gt;
>
>
> > Date: Sat, 11 Jun 2011 19:15:55 -0400
> > From: mhern...@wickedsoftware.net
> > To: lucene-net-dev@lucene.apache.org
> > Subject: Re: [Lucene.Net] Could not load assembly
> >
> > In the past people have
nto 2.9.4g
- there are some caveats - each will have a set of it's own files for some
classes
> Date: Sat, 11 Jun 2011 19:15:55 -0400
> From: mhern...@wickedsoftware.net
> To: lucene-net-dev@lucene.apache.org
> Subject: Re: [Lucene.Net] Cou
y there is another way?
>
>
>
>
>
> > Date: Sat, 11 Jun 2011 18:34:02 -0400
> > From: mhern...@wickedsoftware.net
> > To: lucene-net-dev@lucene.apache.org
> > Subject: Re: [Lucene.Net] Could not load assembly
> >
> > was it co
11 18:34:02 -0400
> From: mhern...@wickedsoftware.net
> To: lucene-net-dev@lucene.apache.org
> Subject: Re: [Lucene.Net] Could not load assembly
>
> was it compiled against the wp7 version of silverlight? or .net full
> framework?
>
> On Sat, Jun 11, 2011 at 6:28 PM, Prescot
n go back and start
> filling in holes (like the test proj)
>
>
>
>
>
> > From: digyd...@gmail.com
> > To: lucene-net-dev@lucene.apache.org
> > Date: Sun, 12 Jun 2011 01:23:35 +0300
> > Subject: RE: [Lucene.Net] Could n
: lucene-net-dev@lucene.apache.org
> Date: Sun, 12 Jun 2011 01:23:35 +0300
> Subject: RE: [Lucene.Net] Could not load assembly
>
> Hard to guess.
>
> Have you seen Contrib.IsolatedStorage.Test.csproj?
>
> DIGY
>
> -Original Message-
> From: Prescott Nasser [mailto:geobmx...
Hard to guess.
Have you seen Contrib.IsolatedStorage.Test.csproj?
DIGY
-Original Message-
From: Prescott Nasser [mailto:geobmx...@hotmail.com]
Sent: Sunday, June 12, 2011 12:33 AM
To: lucene-net-dev@lucene.apache.org
Subject: [Lucene.Net] Could not load assembly
While trying to set up
The easiest way to diagnose these issues is to run fuslogvw.exe from
the .Net SDK command line and choose to log bind failures. Fusion,
the .Net loader, gives a wealth of info about these kind of failures.
After you setup the logging, run the test to failure again; the log
should then point to the
