Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release notes for TestDriven.Net 4.0-beta3 #79

Open
jcansdale opened this issue Dec 12, 2016 · 2 comments
Open

Release notes for TestDriven.Net 4.0-beta3 #79

jcansdale opened this issue Dec 12, 2016 · 2 comments
Assignees
Milestone

Comments

@jcansdale
Copy link
Owner

jcansdale commented Dec 12, 2016

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.

@jcansdale jcansdale added this to the v4.0-beta3 milestone Dec 12, 2016
@jcansdale jcansdale self-assigned this Dec 12, 2016
@jcansdale jcansdale reopened this Dec 12, 2016
@sm-g
Copy link

sm-g commented Jan 16, 2017

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
Copy link
Owner Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants