I have a test project that uses the ASP.NET Core TestServer to host the web project for testing. I've recently upgraded from Asp.NET Core 2.2 targeting net48 to an Asp.NET 3.1 targeting netcoreapp3.1. Previously, NCrunch would copy both the Web Project and the Test project folders into the temp location where NCrunch runs tests.

It looked something like this
AppData\Local\NCrunch\47380\83\TESTPROJECT
AppData\Local\NCrunch\47380\83\WEBPROJECT

This meant that in my TestStartup class I could walk up the folders until I found the folder containing the web project (and ultimately wwwroot). Now, after the upgrade, the web project is no longer copied into the same temp folder as the test project. This means I can no longer find the web project's folder and set the ContentRoot and WwwRoot folder locations. All of my tests now fail because of this.

Is there an article somewhere illustrating how to test an Asp.NET Core 3.X project with NCrunch? The built-in VS Test Runner works fine, so I know it's not my tests, but instead is the way NCrunch copies things to the temp folder.

I am using Microsoft.AspNetCore.Mvc.Testing but no, unfortunately, that doesn't work for me. The structure I'm getting now is this:

AppData\Local\NCrunch\47380\82\WEBPROJECT
AppData\Local\NCrunch\47380\83\TESTPROJECT

Notice WEBPROJECT is under subfolder named 82 while TESTPROJECT is under 83...

Directory.GetCurentDirectory() gives me this:

AppData\Local\NCrunch\47380\83\TESTPROJECT\bin\Debug\netcoreapp3.1\

when what I actually need for content root is the location under the WEBPROJECT. For now, I just walk up directories until I get to the test project's root folder. Then, I go one more and convert the name of the folder into an int. From there I start subtracting (or adding) 1 to the name, and search for the web folder. Once I find it, I set it as the content root. This works, but OH MAN does it feel fragile and unnecessary. I must be missing something.

Ahh, I didn't know about the GetAllAssemblyLocations method, brilliant!

FWIW, it's not the new version of NCrunch that made this start happening. I can run a different branch of the same solution that hasn't been upgraded to Asp.NET Core 3.1 and it works fine. The solution is a bit odd in that it has two websites and about 40 class library projects.

One website is new and based on .net core and the other is legacy and based on classic asp.net MVC 4. They both depended on EF 6, so we were targeting the NET Framework with both websites and all class libraries. With NETStandard 2.1 now supporting EF 6, we went ahead an updated all the class libraries to multi-target netstandard2.1 and net48. The old asp.net project remained as it was, and the new asp.net core project got upgraded to netcoreapp3.1.

This works great, but for some reason NCrunch started behaving differently. I think we are just confusing it though. We have a shared test framework class library that multi-targets, and two other test projects.
One that exercises the legacy site which is still using net48 target and another that exercises the asp.net core site and it targets netcoreapp3.1. The one that targets the net core site is the one that started acting differently.

Thanks for your help!

Hi, thanks for sharing this problem. I'm having some difficulty reproducing it. Are you able to build a sample solution that can reproduce this problem and you can share with me? You can submit code in ZIP form through the NCrunch contact form.