.NET Core/Standard and nUnit
-
So after spending the better part of my Sunday and a good bit of time today trying to get nUnit tests working in a VS2015 .NET Core (netstandard1.6) class library, I gave up and installed VS2017. Took maybe 5 minutes to move code over and everything works fine :doh: Now I'm wondering why it wouldn't work in VS2015 considering it's the same NuGet packages - Microsoft.NET.Test.Sdk 15.5, nUnit 3.9, and nUnit3TestAdapter 3.9. Anyone have a similar issue and find out the cause? I'm just curious at this point. It wouldn't even recognize the tests in VS2015 :confused:
-
So after spending the better part of my Sunday and a good bit of time today trying to get nUnit tests working in a VS2015 .NET Core (netstandard1.6) class library, I gave up and installed VS2017. Took maybe 5 minutes to move code over and everything works fine :doh: Now I'm wondering why it wouldn't work in VS2015 considering it's the same NuGet packages - Microsoft.NET.Test.Sdk 15.5, nUnit 3.9, and nUnit3TestAdapter 3.9. Anyone have a similar issue and find out the cause? I'm just curious at this point. It wouldn't even recognize the tests in VS2015 :confused:
I dunno since I use xUnit now, when I discovered that Microsoft is doing so. xUnit works well in VS2017. I am surprised that NUnit doesn't work for you though.. did you install the VS runner?
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
I dunno since I use xUnit now, when I discovered that Microsoft is doing so. xUnit works well in VS2017. I am surprised that NUnit doesn't work for you though.. did you install the VS runner?
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
Everything works in VS2017 just fine but for some reason wouldn't in VS2015. Same runner which supposedly should work for VS2012 and up (nUnit3TestAdapter 3.9) according to its documentation. So I'm just left scratching my head on what was going wrong in VS2015 :doh:
-
So after spending the better part of my Sunday and a good bit of time today trying to get nUnit tests working in a VS2015 .NET Core (netstandard1.6) class library, I gave up and installed VS2017. Took maybe 5 minutes to move code over and everything works fine :doh: Now I'm wondering why it wouldn't work in VS2015 considering it's the same NuGet packages - Microsoft.NET.Test.Sdk 15.5, nUnit 3.9, and nUnit3TestAdapter 3.9. Anyone have a similar issue and find out the cause? I'm just curious at this point. It wouldn't even recognize the tests in VS2015 :confused:
-
NUnit Visual Studio Project Loader 3.7 Released[^]
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
Unless I'm missing something that is an extension for the nUnit engine/GUI to load VS projects. I was testing inside VS itself with the Test SDK and nUnit3TestAdapter. I tried a few older versions of the NuGet packages in case something broke when they added the
csprojsupport since VS2015 .NET Core class libraries still use theproject.jsonformat but had the same results. Oh well, as good an excuse as any to finally move over to VS2017 for personal projects :thumbsup:
