[
https://issues.apache.org/jira/browse/LUCENENET-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066161#comment-16066161
]
Jens Melgaard edited comment on LUCENENET-565 at 6/28/17 8:57 AM:
------------------------------------------------------------------
{quote}Although I think it would be great to get on .NET Standard 2.0, I don't
think it really helps anything here since we are talking about front-end
applications for HTTP listeners and .NET Standard only affects the sharing of
back-end class libraries among front-end applications{quote}
Not on a functional level no, that is why it was a curiosity question, it looks
like the dependency graph would be much simpler, but that's really just a
detail.
I think I will proceed with AspNetCore 1.1.2 for now, and as you say, It's for
a very small service... And to put that in a even better perspective, this is
only for a single public method... Namely the
ReplicationService.Perform(request, response) method... That's it... So it
should be really easy to decouple later.
I did however run into another road-block as I was so Insane to update Visual
Studio 2017 to the newest version the other day, which now means I can't build
anything as it all complains about the project.json files...
I have not updated on all the different machines I work on, but it does
constrain me quite a bit. :S...
was (Author: jmd):
{quote}Although I think it would be great to get on .NET Standard 2.0, I don't
think it really helps anything here since we are talking about front-end
applications for HTTP listeners and .NET Standard only affects the sharing of
back-end class libraries among front-end applications{quote}
Not on a functional level no, that is why it was a curiosity question, it looks
like the dependency graph would be much simpler, but that's really just a
detail.
I think I will proceed with AspNetCore 1.1.2 for now, and as you say, It's for
a very small service... And to put that in a even better perspective, this is
only for a single public method... Namely the
ReplicationService.Perform(request, response) method... That's it... So it
should be really easy to decouple later.
I did however run into another road-block as I was so Insane to update Visual
Studio 2017 to the newest version the other day, which now means I can't build
anything as it all complains about the project.json files... I have not update
on all the different machines I work on, but it does constrain me quite a bit.
:S...
> 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)
