Open jcansdale opened 7 years ago
sm-g
commented
7 years ago After update to this version I got "No .NET Core element (e.g. 'netcoreapp1.0') is defined in the 'frameworks' element of: D:\Tests\project.json" for my Core project with "frameworks": { "net461"
jcansdale
commented
7 years ago @sm-g Have you installed VS 2017 RC as well? I'm afraid .NET Core tooling has been a mess since this was released.
Knowing project.json is being replaced with .csproj, I don't want to spend too much time keeping it working with old project.json versions. I don't want to touch .NET Core again until the tooling is completely stable! 😢
Sorry I don't have better news for you.
TDI76: Add support for Visual Studio 2017 RC
TestDriven.Net will be installed for Visual Studio 2017 RC (Community, Professional and Enterprise in their default locations).
TDI77: Setup prompts to download .NET 3.5 on Windows 10
Installer (setup.exe) is now built using .NET 4.0 so that is can be installed on a clean installation without .NET 2.0/3.5. Also made NCoverExplorer default to using .NET 4.0.
TDI80: TestDriven.Net doesn't work on a 32-bit OS in Visual Studio 2015+
Fixed issue where TestDriven.Net couldn't find its home directory when running on a 32-bit version of Windows.
TDI83: Test With > NCover doesn't work when .NET 2.0/3.5 isn't installed
Allow NCover/NCoverExplorer to run when just .NET 4.x is installed.
TDI72: Can you put the .csproj context menu buttons back below "build" like in VS2012?
Project context menu buttons are now placed in consistent locations.
TDI65: Update for NUnit 3.5
Update installer to include latest version of NUnit.
TDI71: Test With > NUnit not working in 4.0 Beta 2
Restore option to test using the old NUnit 2.5.10 GUI from project context menu.