Skip to content

Rafael Nieto

My feedback

2 results found

  1. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Rafael Nieto commented  · 

    Thanks. I can see why this "simple" feature request is actually very complicated to implement. However as you say I don't think this is an unusual situation either. Many developers work on big codebases and it's only practical to work with a subset of the projects at a time.

    For now I'll keep using my "hacks" to get around this, or even not using NCrunch in cases where the workarounds are just too much hassle :(

    I do look forward to NCrunch features to better support developers working in these kinds of build environments.

    An error occurred while saving the comment
    Rafael Nieto commented  · 

    Thanks Remco. Yes I do set 'Ignore this project completely' to true by default for all projects. I only unignore those projects that I'm working on to avoid building them and speed up development.

    I'm actually using binary references now as a workaround by placing them inside an ItemGroup node with the NCrunch build variable as a condition. I also use 'Infer project references using assembly names' so that NCrunch knows which of my unignored projects to rebuild.

    However this workaround is not ideal since I have to maintain this binary reference list manually. I know that using project references and letting NCrunch build the whole dependency chain is ideal. However a lot of the referenced projects are owned by other teams. And a lot of those projects have custom build steps which don't play well with NCrunch.

    Even if I fixed all the projects in the dependency chain to work with NCrunch, it would take a very long time to build all of those dependencies each time I create a new branch in git. That is why we have a custom tool to copy the built binaries from the build share.

    I was wondering if msbuild has an API to get the target location of a project. I don't know how NCrunch interacts with msbuild so I'm not sure if that is possible. When I run msbuild from our build environment (which uses BuildProjectReferences=false) it somehow knows where the corresponding binaries are and it builds successfully without having to build the dependency chain.

    Rafael Nieto shared this idea  · 
  2. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Rafael Nieto supported this idea  · 

Feedback and Knowledge Base