Modern Visual Studio extensions are generally installed as a .vsix file. While this offers less flexibility when it comes to install locations and creating registry entries, it means that Visual Studio is responsible for doing the installation. This greatly simplifies installation on VS 2017 (there can be multiple versions installed at a time) and can speed up development.
TestDriven.Net currently relies quite heavily on the registry to find the location of its components and test runners. The plan is to initially offer a stripped down version that only supports modern versions of test runners (NUnit and xUnit). I'd like to also support the NuGet version of MSTest but this will require a lot more work.
It's designed so that it can be installed over the top of the full TestDriven.Net install (in which case all features should light up). If you only install the .vsix, you'll have a light weight version which only supports NUnit 3.0, xUnit and "Ad hoc" tests. It also supports 'Test With > In-Proc (VS SDK)', which I use a lot these days (see #90).
Modern Visual Studio extensions are generally installed as a
.vsixfile. While this offers less flexibility when it comes to install locations and creating registry entries, it means that Visual Studio is responsible for doing the installation. This greatly simplifies installation on VS 2017 (there can be multiple versions installed at a time) and can speed up development.TestDriven.Net currently relies quite heavily on the registry to find the location of its components and test runners. The plan is to initially offer a stripped down version that only supports modern versions of test runners (NUnit and xUnit). I'd like to also support the NuGet version of MSTest but this will require a lot more work.
Here is a super-early, works on my machine release: TestDriven.VSPackage.zip
It's designed so that it can be installed over the top of the full TestDriven.Net install (in which case all features should light up). If you only install the .vsix, you'll have a light weight version which only supports NUnit 3.0, xUnit and "Ad hoc" tests. It also supports 'Test With > In-Proc (VS SDK)', which I use a lot these days (see #90).