lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Melgaard (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LUCENENET-565) Port Lucene.Net.Replicator
Date Fri, 21 Jul 2017 08:24:00 GMT

    [ https://issues.apache.org/jira/browse/LUCENENET-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095950#comment-16095950
] 

Jens Melgaard edited comment on LUCENENET-565 at 7/21/17 8:23 AM:
------------------------------------------------------------------

Hi...

No, even though some projects used the new project.json for nuget, Visual Studio 2017 choose
to use package.json for the projects I added, in the latest commit they have been renamed
to --packages_old as I used script to convert them, although I abandoned that (currently keept
the converted files as .converted, but it seemed I could get to a cleaner file by hand)...

But No, I am strugeling somewhat as well to get both the portable.sln and the regular.sln
to build at the same time, currently only the portable.sln builds but when running tests ReSharper
complains allot and as far as i can tell ReSharper have had some issues with Core projects
(running tests)... So I was going to ask how you where running tests?... (They ran fine under
the normal sln, but there was a few things that had to be switched for .NET Core, nothing
major but I need to ensure that JSON.NET can serialize and deserialze exceptions correctly),


I can try and get back to the point now where the main solution builds... I would certainly
be in favor for moving ahead towards the new .csproj file and a single solution... >.<...


was (Author: jmd):
Hi...

No, even though some projects used the new project.json for nuget, Visual Studio 2017 choose
to use package.json for the projects I added, in the latest commit they have been renamed
to --packages_old as I used script to convert them, although I abandoned that (currently keept
the converted files as .converted, but it seemed I could get to a cleaner file by hand)...

But No, I am strugeling somewhat as well to get both the portable.sln and the regular.sln
to build at the same time, currently only the portable.sln builds but when running tests ReSharper
complains allot and as far as i can tell ReSharper have had some issues with Core projects
(running tests)... So I was going to ask how you where running tests?...

I can try and get back to the point now where the main solution builds... I would certainly
be in favor for moving ahead towards the new .csproj file and a single solution... >.<...

> Port Lucene.Net.Replicator
> --------------------------
>
>                 Key: LUCENENET-565
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-565
>             Project: Lucene.Net
>          Issue Type: Task
>          Components: Lucene.Net.Replicator
>    Affects Versions: Lucene.Net 4.8.0
>            Reporter: Shad Storhaug
>            Priority: Minor
>              Labels: features
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message