You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Granroth, Neal V." <ne...@thermofisher.com> on 2012/08/08 21:07:34 UTC
Lucene.NET 3.0.3 Build issues
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 a newer version.
Opening the solution file in notepad reveals that it was created with VS2012 (a not yet released product)
It would be very helpful if those maintaining the source distribution limit themselves to released development tools only.
It also make me wonder of the viability of any binary distributions; they certainly should not have been created with VS2012RC
- Neal G.
Re: Lucene.NET 3.0.3 Build issues
Posted by "xzxz@mail.ru" <xz...@mail.ru>.
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 a newer version.
> Opening the solution file in notepad reveals that it was created with VS2012 (a not yet released product)
>
> It would be very helpful if those maintaining the source distribution limit themselves to released development tools only.
>
> It also make me wonder of the viability of any binary distributions; they certainly should not have been created with VS2012RC
>
> - Neal G.
>
>
>
+1
Re: Lucene.NET 3.0.3 Build issues
Posted by Christopher Currens <cu...@gmail.com>.
Thanks for the feedback. Let us know if you run into any more
issues/concerns.
Thanks,
Christopher
On Wed, Aug 8, 2012 at 1:33 PM, Granroth, Neal V. <
neal.granroth@thermofisher.com> wrote:
> Yes I pulled from the branch not the trunk. I apparently made the
> incorrect assumption that it would be slightly more stable than the current
> work-in-progress.
>
> Thanks for the quick attention and clarifications. Especially for those
> that rely upon the binary packages.
>
> - Neal
>
>
> -----Original Message-----
> From: Christopher Currens [mailto:currens.chris@gmail.com]
> Sent: Wednesday, August 08, 2012 3:21 PM
> To: lucene-net-dev@lucene.apache.org
> Subject: Re: Lucene.NET 3.0.3 Build issues
>
> 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 <
> currens.chris@gmail.com
> > wrote:
>
> > See inline comments.
> >
> >
> > Thanks,
> > Christopher
> >
> > On Wed, Aug 8, 2012 at 12:07 PM, Granroth, Neal V. <
> > neal.granroth@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 folder.
> >>
> >> Did you pull down the 3.0.3 branch or trunk? Trunk is 3.0.3, I'm not
> > even sure the 3.0.3 branch exists anymore, and if it does, it is very,
> very
> > out of date.
> >
> >
> >> This solution will not load in VS2010, Visual Studio complains that it
> >> was created with a newer version.
> >> Opening the solution file in notepad reveals that it was created with
> >> VS2012 (a not yet released product)
> >>
> >> They are supposed to be VS2010, if the pathing didn't give it away. I
> > believe it was my fault, as I usually will change them back to VS2010
> > manually, but forgot to do that while I was adding .NET 3.5 support back
> > in. In order to automate the change, I needed to use the RC and forgot
> to
> > change the solution files back. As an aside, VS2012 solution files are
> (or
> > at least supposed to be) backwards compatible with VS2010. On my laptop,
> > which only has VS2010 SP1, they open and compile just fine.
> >
> >
> >> It would be very helpful if those maintaining the source distribution
> >> limit themselves to released development tools only.
> >>
> >> Since that's our normal policy, this isn't really an issue.
> >
> >
> >> It also make me wonder of the viability of any binary distributions;
> they
> >> certainly should not have been created with VS2012RC
> >>
> >
> > Prescott used VS2010 to make the binary, so I don't think you need to
> > worry about this.
> >
> >
> >>
> >> - Neal G.
> >>
> >>
> >
>
RE: Lucene.NET 3.0.3 Build issues
Posted by "Granroth, Neal V." <ne...@thermofisher.com>.
Yes I pulled from the branch not the trunk. I apparently made the incorrect assumption that it would be slightly more stable than the current work-in-progress.
Thanks for the quick attention and clarifications. Especially for those that rely upon the binary packages.
- Neal
-----Original Message-----
From: Christopher Currens [mailto:currens.chris@gmail.com]
Sent: Wednesday, August 08, 2012 3:21 PM
To: lucene-net-dev@lucene.apache.org
Subject: Re: Lucene.NET 3.0.3 Build issues
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 <currens.chris@gmail.com
> wrote:
> See inline comments.
>
>
> Thanks,
> Christopher
>
> On Wed, Aug 8, 2012 at 12:07 PM, Granroth, Neal V. <
> neal.granroth@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 folder.
>>
>> Did you pull down the 3.0.3 branch or trunk? Trunk is 3.0.3, I'm not
> even sure the 3.0.3 branch exists anymore, and if it does, it is very, very
> out of date.
>
>
>> This solution will not load in VS2010, Visual Studio complains that it
>> was created with a newer version.
>> Opening the solution file in notepad reveals that it was created with
>> VS2012 (a not yet released product)
>>
>> They are supposed to be VS2010, if the pathing didn't give it away. I
> believe it was my fault, as I usually will change them back to VS2010
> manually, but forgot to do that while I was adding .NET 3.5 support back
> in. In order to automate the change, I needed to use the RC and forgot to
> change the solution files back. As an aside, VS2012 solution files are (or
> at least supposed to be) backwards compatible with VS2010. On my laptop,
> which only has VS2010 SP1, they open and compile just fine.
>
>
>> It would be very helpful if those maintaining the source distribution
>> limit themselves to released development tools only.
>>
>> Since that's our normal policy, this isn't really an issue.
>
>
>> It also make me wonder of the viability of any binary distributions; they
>> certainly should not have been created with VS2012RC
>>
>
> Prescott used VS2010 to make the binary, so I don't think you need to
> worry about this.
>
>
>>
>> - Neal G.
>>
>>
>
Re: Lucene.NET 3.0.3 Build issues
Posted by Christopher Currens <cu...@gmail.com>.
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 <currens.chris@gmail.com
> wrote:
> See inline comments.
>
>
> Thanks,
> Christopher
>
> On Wed, Aug 8, 2012 at 12:07 PM, Granroth, Neal V. <
> neal.granroth@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 folder.
>>
>> Did you pull down the 3.0.3 branch or trunk? Trunk is 3.0.3, I'm not
> even sure the 3.0.3 branch exists anymore, and if it does, it is very, very
> out of date.
>
>
>> This solution will not load in VS2010, Visual Studio complains that it
>> was created with a newer version.
>> Opening the solution file in notepad reveals that it was created with
>> VS2012 (a not yet released product)
>>
>> They are supposed to be VS2010, if the pathing didn't give it away. I
> believe it was my fault, as I usually will change them back to VS2010
> manually, but forgot to do that while I was adding .NET 3.5 support back
> in. In order to automate the change, I needed to use the RC and forgot to
> change the solution files back. As an aside, VS2012 solution files are (or
> at least supposed to be) backwards compatible with VS2010. On my laptop,
> which only has VS2010 SP1, they open and compile just fine.
>
>
>> It would be very helpful if those maintaining the source distribution
>> limit themselves to released development tools only.
>>
>> Since that's our normal policy, this isn't really an issue.
>
>
>> It also make me wonder of the viability of any binary distributions; they
>> certainly should not have been created with VS2012RC
>>
>
> Prescott used VS2010 to make the binary, so I don't think you need to
> worry about this.
>
>
>>
>> - Neal G.
>>
>>
>
Re: Lucene.NET 3.0.3 Build issues
Posted by Christopher Currens <cu...@gmail.com>.
See inline comments.
Thanks,
Christopher
On Wed, Aug 8, 2012 at 12:07 PM, Granroth, Neal V. <
neal.granroth@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 folder.
>
> Did you pull down the 3.0.3 branch or trunk? Trunk is 3.0.3, I'm not even
sure the 3.0.3 branch exists anymore, and if it does, it is very, very out
of date.
> This solution will not load in VS2010, Visual Studio complains that it was
> created with a newer version.
> Opening the solution file in notepad reveals that it was created with
> VS2012 (a not yet released product)
>
> They are supposed to be VS2010, if the pathing didn't give it away. I
believe it was my fault, as I usually will change them back to VS2010
manually, but forgot to do that while I was adding .NET 3.5 support back
in. In order to automate the change, I needed to use the RC and forgot to
change the solution files back. As an aside, VS2012 solution files are (or
at least supposed to be) backwards compatible with VS2010. On my laptop,
which only has VS2010 SP1, they open and compile just fine.
> It would be very helpful if those maintaining the source distribution
> limit themselves to released development tools only.
>
> Since that's our normal policy, this isn't really an issue.
> It also make me wonder of the viability of any binary distributions; they
> certainly should not have been created with VS2012RC
>
Prescott used VS2010 to make the binary, so I don't think you need to worry
about this.
>
> - Neal G.
>
>
RE: Lucene.NET 3.0.3 Build issues
Posted by Prescott Nasser <ge...@hotmail.com>.
I use VS2010 and they opened fine for me to cut the pre-release nuget packages. I'll try to take a in the next day or two to see if I can't move that back to a VS2010 package.
I wouldn't have an issue with a VS2012 solution file - as long as it was in VS2012 build folder, not the VS2010 folder; and we had a VS2010 solution.
Thanks for the heads up
~P
----------------------------------------
> From: neal.granroth@thermofisher.com
> To: lucene-net-dev@lucene.apache.org
> Date: Wed, 8 Aug 2012 12:07:34 -0700
> Subject: Lucene.NET 3.0.3 Build issues
>
> 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 a newer version.
> Opening the solution file in notepad reveals that it was created with VS2012 (a not yet released product)
>
> It would be very helpful if those maintaining the source distribution limit themselves to released development tools only.
>
> It also make me wonder of the viability of any binary distributions; they certainly should not have been created with VS2012RC
>
> - Neal G.
>