08.08.2012 23:07, Granroth, Neal V. пишет:
I just pulled down the 3.0.3 branch from SVN and have encountered an initial
problem with the VisualStudio solution file Lucene.Net.Core.sln in the VS2010
folder.
This solution will not load in VS2010, Visual Studio complains that it was
created with
See inline comments.
Thanks,
Christopher
On Wed, Aug 8, 2012 at 12:07 PM, Granroth, Neal V. <
neal.granr...@thermofisher.com> wrote:
> I just pulled down the 3.0.3 branch from SVN and have encountered an
> initial problem with the VisualStudio solution file Lucene.Net.Core.sln in
> the VS2010 f
FYI - SVN has been updated with corrected VS2010 solutions and added VS2012
directory/solution files.
On Wed, Aug 8, 2012 at 1:12 PM, Christopher Currens wrote:
> See inline comments.
>
>
> Thanks,
> Christopher
>
> On Wed, Aug 8, 2012 at 12:07 PM, Granroth, Neal V. <
> neal.granr...@thermofishe
I just created 3.0.3 last weekend - it should be incredibly up to date.
Anything in trunk should be there
Sent from my Windows Phone
From: Christopher Currens
Sent: 8/8/2012 1:35 PM
To: lucene-net-dev@lucene.apache.org
Subject: Re: Lucene.NET 3.0.3 Build issues
T
Oh, did you do that so we'd have a branch to do bug fixes? I had forgotten
about that.
On Wed, Aug 8, 2012 at 2:23 PM, Prescott Nasser wrote:
> I just created 3.0.3 last weekend - it should be incredibly up to date.
> Anything in trunk should be there
>
> Sent from my Windows Phone
> ___
Yes
Sent from my Windows Phone
From: Christopher Currens
Sent: 8/8/2012 4:22 PM
To: lucene-net-dev@lucene.apache.org
Subject: Re: Lucene.NET 3.0.3 Build issues
Oh, did you do that so we'd have a branch to do bug fixes? I had forgotten
about that.
On Wed, Aug 8,
I think it's usually the project files that are backwards compatible not
the solution files. So you need a solution for each vs version but should
be able to keep the proj files the same.
On Wed, Aug 8, 2012 at 7:27 PM, Prescott Nasser wrote:
> Yes
>
> Sent from my Windows Phone
> ___
It used to be that way. VS2012 is the first version that produces
backwards compatible projects *and* solutions. There's an msdn blog
entry[1] that discusses it. It does focus more projects, but starts with
discussing solutions and how having it all backwards compatible would ease
transitions for
