Github user NightOwl888 commented on the issue:
https://github.com/apache/lucenenet/pull/191
>
> 1. From command line: dotnet restore
> 2. Open Lucene.Net.Portable.sln
> 3. Right-click -> Build Solution (Ctrl+Shift+B)
>
> Do you still get the errors "An item
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
Github user conniey commented on the issue:
https://github.com/apache/lucenenet/pull/191
> I gave my VS 2012 Professional a shot, but there doesn't appear to be a
test runner for NUnit 3.5 in this environment. I am down to running the tests
on the command line for lack of
Github user NightOwl888 commented on the issue:
https://github.com/apache/lucenenet/pull/191
Prescott,
Thanks. Iâd appreciate it. It would be better if we could consolidate all
development on Visual Studio 2015 Community so others that want to contribute
donât have to
Github user NightOwl888 commented on the issue:
https://github.com/apache/lucenenet/pull/195
No offense, but since @conniey has already provided a [working solution to
the ICU bitness
issue](https://github.com/apache/lucenenet/pull/191#issuecomment-262379449),
this seems like a step
Github user synhershko commented on the issue:
https://github.com/apache/lucenenet/pull/195
ð
WDYT @NightOwl888 ?
---
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
GitHub user laimis opened a pull request:
https://github.com/apache/lucenenet/pull/195
Moving ICU dependent classes into a separate project
Would this help to deal with ICU issues that people are encountering in
using early versions of 4.8 port? Seems like a quick way to get past
