Github user NightOwl888 commented on the issue:
https://github.com/apache/lucenenet/pull/191
Here's the file...
[restore.zip](https://github.com/apache/lucenenet/files/610313/restore.zip)
NOTE: Despite what I said earlier about not wasting effort on .NET 3.5, we
should probably keep that door open depending on how much demand there is for
it once we get onto NuGet. For Spatial4n, I was unable to get a portable
library to work as far back as .NET 3.5, so having a .csproj around for the old
stack might be the only solution.
I came up with a different solution for Spatial4n - separate project
directories, the legacy stack using only linked files. Its fine for that small
project, but won't scale up for this one well.
> Sorry if I am missing context... are you trying to test out #194? You can
open the existing Lucene.Net.sln solution in Visual Studio 2015 already. I can
get you a copy of Visual Studio 2013 though on Friday (when everyone goes back
to work).
Ahh, that is something I didn't try before (it says above it won't work
with VS2015). I just tried it and I am also getting errors going down that road
- here is a screenshot.
My environment is Windows 10 Pro x64 with VS2015 Community + .NET Core SDK
1.0.1 Preview 2
Do note I tried building with Visual Studio before running the tests.
Should I be building from the command line instead?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
