After the upheaval of moving offices, I am starting to settle into my new normal routine. Overall I am much happier in my new hole in the ground. Business was crazy but has tapered off a bit as summer starts its decline in earnest. During this break, I am learning .NET CORE in preparation for the release of .NET Framework 5 this November. In doing this I ran into a slight problem with NUnit and Visual Studio.
While I did not feel it was worth the trouble to upgrade to Visual Studio 2019 when I was using .NET Framework, the advantages gained by doing that to get CORE 3 are well worth the trouble. I am currently in the process of learning CORE and so I have moved into CORE 3 but I ran into a little issue.
My test tab was missing and I could not run my unit tests. It ain’t easy to run your NUnit tests in Visual Studio when your shit is missing.
Image Box Title
Change this description
![NUnit is missing in Visual Studio](https://i0.wp.com/siliconprairiedog.com/wp-content/uploads/2020/09/1-Missing-testing-tab.png?resize=1728%2C936&ssl=1)
As I use NUnit for my unit tests, installing crap to get them going is a normal mode of business but this was different. I always forget the process to do when I need to get that tab windows up and running. As a result of my forgetful ways, I am going to document it for me and you. Lets dig into it.
Start Fixing Nunit and Visual Studio by Getting the Extension needed.
Image Box Title
Change this description
![](https://i0.wp.com/siliconprairiedog.com/wp-content/uploads/2020/09/3-Get-Extensions.png?resize=1729%2C943&ssl=1)
Start by going to Extension=>Manage Extension.
Image Box Title
Change this description
![](https://i0.wp.com/siliconprairiedog.com/wp-content/uploads/2020/09/4-NUnit-Test-Adapter.png?resize=1729%2C943&ssl=1)
Grab your NUnit Test adapter and press the Download button.
Image Box Title
Change this description
![](https://i0.wp.com/siliconprairiedog.com/wp-content/uploads/2020/09/5-Close-Everything-and-let-it-install.png?resize=1729%2C943&ssl=1)
After that close everything so that the installer can do it thing. Note you will have to close all Visual Studio instance. I think that includes SQL Server Management instance though I did not test this.
Image Box Title
Change this description
![](https://i0.wp.com/siliconprairiedog.com/wp-content/uploads/2020/09/6-Starts-installing.png?resize=436%2C332&ssl=1)
Watch it bump and grind.
Image Box Title
Change this description
![](https://i0.wp.com/siliconprairiedog.com/wp-content/uploads/2020/09/7-Confirm-Install.png?resize=436%2C332&ssl=1)
Accept the modifications to Visual Studio by pressing the Modify button.
Image Box Title
Change this description
![](https://i0.wp.com/siliconprairiedog.com/wp-content/uploads/2020/09/8-Installing.png?resize=436%2C332&ssl=1)
If you failed to get everything closed, exterminate the offending software through the End Tasks button.
Enjoy the bumping and grinding some more.
Image Box Title
Change this description
![](https://i0.wp.com/siliconprairiedog.com/wp-content/uploads/2020/09/9-Continue-Installing.png?resize=436%2C332&ssl=1)
![](https://i0.wp.com/siliconprairiedog.com/wp-content/uploads/2020/09/10-Install-Complete.png?resize=436%2C332&ssl=1)
Finally, it will be done. Press the close button and open Visual Studio.
Image Box Title
Change this description
![Test Results become available so now you can use NUnit in Visual Studio.](https://i0.wp.com/siliconprairiedog.com/wp-content/uploads/2020/09/11-Open-Test-Results.png?resize=1725%2C941&ssl=1)
Now, this is stupid easy but I have to look it up every single time, I switch IDE’s so hopefully, I won’t have that issue with NUnit any longer and neither will you.
My pace of posting will likely be less and more erratic. I am learning a bunch of new stuff and starting to gear up on my first independent piece of software. It is exciting and I will be giving updates as I do. Right now I am finalizing the details of the app and what technology stack I am going to use. Right now, I will be building it in .NET CORE but the front end is more of a mystery. There are a couple of candidates, including giving Xamarin another try.