Sounds good to me. At some point I'd like to address namespace mappings too... But perhaps that's best deferred for the 3.x reworking?
Also, there are a number of less-than-useful documentation files (html) and other random files that seem to come from the Java world. It would be nice to clean up the source tree and get rid of that stuff. Also, we don't have a system for generating the MSDN style documentation at the moment. When we set up the CI server, it'd be nice if it could convert the XML documentation files we're generating into HTML docs. Thanks, Troy On Fri, Feb 25, 2011 at 12:20 PM, Digy <digyd...@gmail.com> wrote: > What about this source tree? > RC2 > ....build > ....contrib > ....core > ........Lucene.Net > ........Test > ....demo > > "src" doesn't mean anything since other dirs contain sources as well. > > DIGY > > -----Original Message----- > From: Troy Howard (JIRA) [mailto:j...@apache.org] > Sent: Friday, February 25, 2011 9:18 PM > To: lucene-net-dev@lucene.apache.org > Subject: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to > VS2010 > > > [ > https://issues.apache.org/jira/browse/LUCENENET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999481#comment-12999481 > ] > > Troy Howard commented on LUCENENET-377: > --------------------------------------- > > I did another version of this for the 2.9.2-incubating-RC2 build. > > Have a look at: > > https://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_9_2_RC2 > > I placed all .sln files, as VS2010 format, in a ~/build/ directory, and > updated the Release profiles to build to a ~/bin/ and ~/doc/ directories. > This makes for better releases packaging structure and consolidates all > solution files to a single directory (no more hunting them down). > > I made my changes on that branch, but could merge them in somewhere (vs2010 > branch or trunk) if we like this layout/design. We also really need to > address naming and namespaces. They are all over the place. I had to update a > lot of things to make it all make sense. Test.dll is really inadequate > naming!! I'll say more on namespaces later, in another context... > > Regarding VS2010 files in general, Neal brings up an interesting problem > case: MsBuild 2.0 or 3.5 pre SP1 can't build a VS2010 file (even if it's > target version is set to 2.0). We either need to set our standard high for > end users (require .NET 3.5 SP1 or higher, and/or Visual Studio 2010), or > provide VS2008 compatible versions of the solution and project files. > > > > >> 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 > > > >
