I prefer it that way as well, but the current setup has one for each project. I guess it makes sense for the Contrib projects because the folks who developed them probably worked on them in isolation from the rest of Lucene.Net.
Anyway, I'd be happy to have less files to maintain. ;) If they don't have a solid and obvious purpose, axe them. Thanks, Troy On Fri, Feb 25, 2011 at 2:59 PM, Wyatt Barnett <wyatt.barn...@gmail.com> wrote: > One thing I'm not quite following -- why does one need a solution for > every single project? Point of solution files is so one can have > multiple projects linked in realish time, so we probably need a single > solution for everything or perhaps two covering core lucene and > contrib. > > > On Fri, Feb 25, 2011 at 5:51 PM, Prescott Nasser (JIRA) <j...@apache.org> > wrote: >> >> [ >> https://issues.apache.org/jira/browse/LUCENENET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999618#comment-12999618 >> ] >> >> Prescott Nasser commented on LUCENENET-377: >> ------------------------------------------- >> >> probably should wipe out the vs2010 branch in all honesty... >> >>> Upgrade solution to VS2010 >>> -------------------------- >>> >>> Key: LUCENENET-377 >>> URL: https://issues.apache.org/jira/browse/LUCENENET-377 >>> Project: Lucene.Net >>> Issue Type: Task >>> Components: Lucene.Net Core >>> Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 3.x >>> Reporter: Jeffrey Cameron >>> Assignee: Prescott Nasser >>> Labels: solution >>> Fix For: Lucene.Net 2.9.4 >>> >>> Attachments: lucene.zip >>> >>> Original Estimate: 10m >>> Remaining Estimate: 10m >>> >>> VS2005 is quite out of date now and there are many new improvements in >>> VS2010. You can still leave the framework support at .NET 2.0 if you like. >> >> -- >> This message is automatically generated by JIRA. >> - >> For more information on JIRA, see: http://www.atlassian.com/software/jira >> >> >> >
