Brondahl

Posts by Brondahl

1. Old version support for new VS versions

   Yep, that's pretty much the answer I was expecting, and seems perfectly reasonable. Here's hoping that VS becomes more stable compatibility-wise going forward; I can vaguely imagine how frustrating it must be to have to work so hard just to stay in the same place. Thanks for the quick response. …

   8 years ago 11 Feb 2018 22:49 UTC

2. Old version support for new VS versions

   Hi, I have a license for an old version of NCrunch (2.13, though I doubt that matters). I have recently upgraded my Visual Studio install to VS2017 - the Free Community version. It looks like my old NCrunch doesn't support VS2017 (it's not present when I open VS, and on the downloads page it …

   8 years ago 11 Feb 2018 17:14 UTC

3. Forcing priority of tests

   Hiya, Shucks, but I'm not terribly surprised. Thanks for the Atomic tip, I've now applied that. It's not so much the through-put as trying to reduce the edit-waitForTests-green cycle. Especially at the moment I've been trying to rebase/merge two wildly conflicting pieces of code, there's been…

   8 years ago 26 Jan 2018 12:53 UTC

4. Forcing priority of tests

   Quote from another thread: [quote] At the moment, NCrunch's prioritisation system works as follows: High priority (targeted by UI) +10000 Failing test +100 Impacted test +300 Test never run before +200 Test is pinned +200 There are then modifications of these values as the tests are gr…

   8 years ago 25 Jan 2018 13:22 UTC

5. Throws exception when using Ninject.Extensions.Conventions

   Hi Remco, Thanks for outlining your views. I started writing a post explaining why I disagree, centred around an argument that the Conventions library is specifically about loosely matching Assemblies by examining the Assemblies it can see around it. ... Except half way through I realised that i…

   8 years ago 05 Jan 2018 22:53 UTC

6. Throws exception when using Ninject.Extensions.Conventions

   Hi there, I'm having the same issues and expect the correct solution to be "Copy Referenced Assemblies To Workspace" from the previously mentioned page of docs. Those docs do have a note saying "In situations where NCrunch detects a well known framework that requires assemblies to be collocated, …

   8 years ago 02 Jan 2018 19:13 UTC

7. Running Build and Post-Build Steps against the original solution [SOLVED]

   Thanks Remco, that's all working perfectly now. I started with code to copy into the core folder, as the first step to get the tests passing, then did some heavy duty refactoring to end up with a PathProvider dependency, which gets a injected differently if NCrunch is active and uses that GetAllA…

   8 years ago 10 Dec 2017 12:05 UTC

8. Running Build and Post-Build Steps against the original solution [SOLVED]

   [quote]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[/quote] Yes, indeed. Further this is a logical dependency, not merely an implementation detail ... Those tests a…

   8 years ago 29 Nov 2017 09:33 UTC

9. Running Build and Post-Build Steps against the original solution [SOLVED]

   (Lots of intro, as I suspect I may have an X-Y problem...) [b]====================== Massive Context and Preamble ====================== [/b] I have a solution which is doing some stuff about opening and using DLLs. Naturally some of that stuff is dependant upon what classes and interfaces ar…

   8 years ago 28 Nov 2017 09:05 UTC