Forum member
Remco NCrunch Developer
7586 posts
Posts by Remco
-
Package error
Hi, This is a VS install state issue. For some reason, VS hasn't refreshed it's extension cache after the MSI was run. To fix this, run 'devenv.exe /setup' as an administrator and wait for this to finish processing in the background.
29 Nov 2017 03:42 UTC
-
Running Build and Post-Build Steps against the original solution [SOLVED]
Hi, thanks for posting. By having the post build steps copying these DLLs into your resource location, you've effectively introduced an implicit dependency from DLLReader.Tests to your TestCaseExamples. This is not a dealbreaker and it can be handled, it just needs a bit more plumbing. You'll…
28 Nov 2017 22:26 UTC
-
.NET Core 2.x fails on DotNetCliToolReference with * as Version number
Hi, thanks for sharing this problem. Yes, this makes sense. The DotNetCliToolReferences aren't represented in project.assets.json, so NCrunch has to do special parallel logic to identify this dependency. I wasn't aware that the '*' option existed, so naturally NCrunch can't handle it. I'll s…
28 Nov 2017 08:55 UTC
-
How can we test the new C# 8.0/Experimental features?
Hi, NCrunch sits atop the build system, so it will use whatever MSBuild does. The version of MSBuild used by NCrunch is that same as the one installed in the instance of Visual Studio you're using (i.e. C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin). This mea…
28 Nov 2017 06:14 UTC
-
Recomendations for working with local db/sqlserver
The best approach I've found here is by using transactions to isolate activities in the database, making sure you roll back a transaction at the end of your test run, and never commit. In this way, your database is always left in a known state. Some ORMs use a pattern of storing the transaction …
27 Nov 2017 11:15 UTC
-
ncrunch 3.12.0.15
It will run in the background. Wait until it's finished before you try to re-run VS.
27 Nov 2017 11:02 UTC
-
ncrunch 3.12.0.15
Sorry, make sure you run it as an administrator.
27 Nov 2017 10:57 UTC
-
ncrunch 3.12.0.15
VS has an internal cache of extensions that are installed. This cache includes a range of important information about extensions, such as their primary DLL, menu options, etc. If something didn't go right during installation, it's possible that the cache is out of date. This may be why it's loo…
27 Nov 2017 10:55 UTC
-
Core 2.0 test project not able to read deps
If this is the same as the known problem, there will be a limited number of Nuget references affected by this. The root of the issue is that NCrunch still supports .NET Core 1.1, so all of its .NET Core libraries are compiled to this version of the framework. Because the referencing system is di…
27 Nov 2017 10:38 UTC
-
ncrunch 3.12.0.15
Sorry, thanks for confirming this. Could you check if you're able to open the nCrunch.VSIntegration2017.dll using any other tool on your machine? (i.e. even notepad). This error suggests that something is blocking access to this file or one of its dependencies. Are you running a virus scanner or …
27 Nov 2017 10:35 UTC
-
Core 2.0 test project not able to read deps
NCrunch is reliant on Visual Studio restoring Nuget packages for it. In the early stages of integration with .NET Core, NCrunch tried to do this itself, but it only caused chaos. If you're seeing this consistently after resetting the engine, check to make sure you have a Nuget dependency on Syst…
27 Nov 2017 10:28 UTC
-
ncrunch 3.12.0.15
Did you install this manually from ZIP previously? This looks like a blocked file issue. Try the [url=http://www.ncrunch.net/documentation/V3/troubleshooting_installation-and-setup-problems]removal and reinstall fix[/url]. If installing manually, make sure you follow the [url=http://www.ncrunch…
27 Nov 2017 10:22 UTC
-
Console/Command window flashing
Hi, There are two possibilities here: 1. You have a build task that is creating a console window when NCrunch builds your projects 2. You have test code that either directly or indirectly causes the creation of a console window To tell between these two, try running NCrunch in the 'Run all…
25 Nov 2017 08:40 UTC
-
Ignored tests and .v3.ncrunchproject-files
Hi, thanks for posting! There are two ways of using NCrunch's ignored tests feature, and nothing in between: 1. You use it to temporarily ignore tests for yourself that you don't want to focus on running. In this case, make sure you have the 'Share tests ignored by NCrunch' setting set to 'Fa…
23 Nov 2017 22:24 UTC
-
Test using Owin TestServer fails
Try the build below and see how you go. We've had some on and off issues with TestHost over the last few months, and I'm aware of at least one problem existing in the v3.11 release that we've managed to fix: [url=http://downloads.ncrunch.net/NCrunch_Console_3.12.0.14.msi]http://downloads.ncrunch…
22 Nov 2017 21:46 UTC
-
Test using Owin TestServer fails
Thanks. Are you using Microsoft.AspNet.TestHost?
22 Nov 2017 10:14 UTC
-
Test using Owin TestServer fails
Hi Jonas, My best guess would be that the server can't find its end-points when it is being hosted in an NCrunch workspace. I recommend taking a look at your test project when it is hosted in the NCrunch workspace (right click on the test project in the Tests Window, go to Advanced->Browse to …
22 Nov 2017 08:14 UTC
-
Since upgrading to v3.11+ NCrunch Tests window in VS2015 reports 1 project failing to build
Hi Steve, Sorry about this. There is a known regression in 3.11 that can cause this problem on some solutions. The build below contains a fix for this: [url=http://downloads.ncrunch.net/NCrunch_Console_3.12.0.14.msi]http://downloads.ncrunch.net/NCrunch_Console_3.12.0.14.msi[/url] [url=http:…
21 Nov 2017 22:26 UTC
-
.NET 4.7.1 Support
This would be an install state issue. Try the following: - Close all IDE windows - Ensure all installed files under "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Remco Software" are completely removed. - Run "C:\Program Files (x86)\Microsoft Visual Studi…
21 Nov 2017 04:04 UTC
-
NetCore2 projects don't get X on exception lines
We have a workaround!!! Make sure you have "C:\Program Files\dotnet\shared\Microsoft.NETCore.App\2.0.0" included in your PATH environment variable.
21 Nov 2017 03:23 UTC