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 deal with this, too. But getting a copy of VS 2013 Professional 
would solve this for the short term.
    
    Connie, do you think it is possible to utilize VS 2015 for development on 
both .NET frameworks?
    
    Either way, now that we have a (build script) solution to getting up on 
NuGet, finding a solution to be able to support development more easily (which 
is the only thing currently blocking us from merging 
https://github.com/apache/lucenenet/pull/191) takes priority over Collation 
(https://github.com/conniey/lucenenet/pull/25). I am still unable to build 
Lucene.Net.Portable.sln in VS 2015, although it works on the command line. 
Since I also don’t have VS 2013 Pro and VS 2012 doesn’t support NUnit 3.5, 
it means the only way I can currently step through tests on #191 is with some 
hackery in VS2012, and the only way I can view test results is on the command 
line.
    
    
    Thanks,
    Shad Storhaug (NightOwl888)
    
    
    From: Prescott Nasser [mailto:[email protected]]
    Sent: Wednesday, November 23, 2016 9:30 AM
    To: apache/lucenenet
    Cc: Shad Storhaug; Mention
    Subject: Re: [apache/lucenenet] Migrating Lucene.Net to .NET Core (#191)
    
    Shad -
    
    You can get a gratis msdn license from MSFT. This comes with $150 azure 
credits and basically any MSFT license you'll ever need.
    
    Ill dig up the form tonight
    
    P
    
    Sent from my Windows Phone
    ________________________________
    From: Shad Storhaug<mailto:[email protected]>
    Sent: ‎11/‎22/‎2016 5:55 PM
    To: apache/lucenenet<mailto:[email protected]>
    Subject: Re: [apache/lucenenet] Migrating Lucene.Net to .NET Core (#191)
    
    
    Thanks Connie. I am having my first stab at working with this branch, but I 
am having a few problems getting set up.
    
    First of all, I don't have a copy of Visual Studio 2013 developer. I have a 
copy of Visual Studio 2013 Web Developer, but I never use it because I cannot 
install the useful test runner and Git extensions. I tried it, but there is a 
lot of friction without these tools.
    
    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 alternatives. As such, this is going to be a 
roadblock for me to maintain this project effectively. Any chance you can talk 
to someone @ Microsoft to see if you can get me an honorary copy of Visual 
Studio 2013 Developer? Or, disregard if the plan is to get us onto VS 2015 
Community exclusively before this branch is merged.
    
    Secondly, I am getting some errors when building Lucene.Net.Portable.sln 
using Visual Studio 2015 Community. Here is a screenshot. The issue appears to 
stem from line 262 in C:\Program Files 
(x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Common.Targets
 on my machine.
    
    
[image]<https://cloud.githubusercontent.com/assets/1538288/20548777/fbe5abbc-b158-11e6-838b-422b2e0d5378.png>
    
    I have both VS2015 update 3 and the .NET Core 1.0.1 SDK installed. Perhaps 
there is another prerequisite that was missed?
    
    —
    You are receiving this because you are subscribed to this thread.
    Reply to this email directly, view it on 
GitHub<https://github.com/apache/lucenenet/pull/191#issuecomment-262418262>, or 
mute the 
thread<https://github.com/notifications/unsubscribe-auth/AAodgwvOhetr-qhSGMyw2xWf0EXFOi8Aks5rA5z4gaJpZM4Klhl7>.
    
    
    —
    You are receiving this because you were mentioned.
    Reply to this email directly, view it on 
GitHub<https://github.com/apache/lucenenet/pull/191#issuecomment-262422061>, or 
mute the 
thread<https://github.com/notifications/unsubscribe-auth/ABd48Igj4s3XahsZz_981nMZ6kAnymO5ks5rA6UggaJpZM4Klhl7>.



---
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.
---

Reply via email to