Skip to content

Feature Requests

I suggest you ...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

58 results found

  1. Support .NET framework 4.7.2

    Currently, NCrunch supports up to 4.7.1.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Support multiple Visual Studio 2017 Installations

    If you install NCrunch to Visual Studio 2017 you cannot selected to which instance the installation should go.

    NCrunch picks one, and install. As a Workaround it is possible to do manual Installation with is not that complicated, but needs several steps, which also needs administration rights.

    This makes upgrading to newer Version a real pain point. Also it might not be a great first impression for new Users. If they don't find NCrunch after installation.

    A Solution might be to switch from MSI to VSIX for VS2017 and following Version.

    11 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    completed  ·  AdminRemco Mulder (NCrunch Developer, NCrunch Website) responded

    We’ve found an unconventional but effective way to rope multi-instance support for VS2017 into the NCrunch MSI installer. The installer should now automatically install for up to 3 instances of VS2017. If you’re using more than 3 instances of VS2017, you can still install NCrunch using the manual installation option.

    This has been released with v3.16.

  3. Support the new PackageReference nodes in VS 2017 project files.

    Currently NCrunch can't build projects that use the new PackageReference structure for NuGet packages as opposed to the "old" packages.config.

    Workaround is to use the old method.

    6 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Increase startup speed in VS2017

    Please, increase the startup speed in Visual Studio 2017. Every now and then it shows me a window with extension-related startup delays, and asking to disable them.

    8 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    completed  ·  AdminRemco Mulder (NCrunch Developer, NCrunch Website) responded

    We’ve done a bit of work in this area over the years. There have also been versions of VS that would often blame VS packages for slow startups unfairly (i.e. when the problem is actually in VS).

    I haven’t seen any notifications of slow startups for a while, nor any recent complaints about this.

    So I think we’re good here.

  5. Support for Visual Studio 15

    At the time of writing Visual Studio 15 is out in preview 5. When can we expect a NCrunch installer for VS 15?

    10 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. Add support for MSTest V2

    Please add support for MSTest V2. This update to MSTest has been available from Microsoft for VS 2015 since June 2016: https://blogs.msdn.microsoft.com/visualstudioalm/2016/06/17/taking-the-mstest-framework-forward-with-mstest-v2/. Since this will be the default engine for VS15 you're going to have to support it at some point. Since it is already available for VS 2015 I'd like to get NCrunch support for that without waiting until VS15 is supported by NCrunch.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. Support .NET Core

    I'm new to NCrunch. I've just seen on Pluralsight and fell in love with it at first sight.

    However, I'm working in a project platformed on .NET Core.
    Do you plan to support it in the near future?
    (Maybe if lots of us vote?)

    39 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Pin all test under the tests tree node

    It would be nice to have ability to pin all tests inside specific node in the "Tests" window. Currently it only works for classes. It would be super convenient to have it working with other nodes (based on groupping) - namespaces, projects, ect.

    7 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. Make use of ExcludeFromCodeCoverage .net framework attribute

    there is already this attribute in framework, most of code coverage tools make use of it, why not to use it.

    https://msdn.microsoft.com/en-us/library/system.diagnostics.codeanalysis.excludefromcodecoverageattribute(v=vs.110).aspx

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. HTML encode span text for AllResults.html file

    So if you have a test case that contains an opening HTML tag and not a closing tag the AllResults report becomes mangled.

    My TestCase: [TestCase("<div>")]

    Generated HTML by the NCrunch console tool: <span class='name'>TestNCrunch.Class1.Test01("<div>")</span>

    really it should be this: <span class='name'>TestNCrunch.Class1.Test01("<div>")</span>

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  11. Disable conhost host

    In process explorer you can see that every nCrunch.TextHost452.x86.exe load a conhost process, which isn't really needed, so it's just wasting performance and resources and fixing this would be really easy. (In Visual Studio for example just set project type of your exe to windows application)

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. Save to project/solution config which tests to run/ignore

    We have a large number of tests. Sadly not all of them are true unit tests and require external systems to started prior to the test.

    It seems if I Ignore all tests and then un-ignore a select few I want to run in Ncrunch there is no way to save this config and commit it to source control. This means each user on the dev team has to do something similar but there is no way to share what tests we want ncrunch to always run.

    I am thinking something similar to what ReSharper allows you to do. It…

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. Ability to create global engine modes, and set default engine mode globally.

    I've created a "Run all unit tests automatically" engine mode in multiple projects because I don't see how I can create a new global engine mode, and set a global default engine mode. This would be a time big time saver!

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. Solution-level defaults for all projects

    There are some settings that we need on every single project within our solution. Currently this means we need a .ncrunchproject file next to every single project with this setting.

    It would be nice if we could set this once in the .ncrunchsolution file instead.

    For bonus points, the individual projects could then override that new default value in their own .ncrunchproject file.

    FYI - The existing value I need this for is UseBuildPlatform=x64, which is set globally in one of our msbuild rules, but not specifically set in every single .csproj file. I'd don't want to need to set…

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  15. Turn off rosyln analyzers during NCrunch Build

    Inspired by post http://forum.ncrunch.net/yaf_postsm7582_Build-fails-with-custom-analyzers.aspx

    Rosyln analyzers in Visual studio 2015 get run during NCrunch Builds. Would it speed up compilation if analyzers were turned off in NCrunch?

    I cant think of a reason why it is necessary - Visual studio gives you real time feedback in the editor and on manual compiles. I wouldn't watch the NCrunch output window for build warnings

    6 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  16. Store NCrunch configuration files as UTF-8

    NCrunch stores its configuration settings in UTF-16. GIT sees that as binary file, and doesn’t show the text diff, even though, they’re just xml files.

    I know you can configure GIT to show those changes (using, for example) the vimdiff tool, but that’s ugly).

    I converted my files to UTF-8, but when you make changes through the NCrunch settings dialog, they’re converted back to UTF-16 :(

    Could the settings of NCrunch be stored as UTF-8, or at least, maintain the encoding on disk?

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  17. Warn when your licence won't be valid for the next version

    When notifying a user when there is a new version of NCrunch to download, add a warning if their licence won't cover the new version.

    This would be preferable compared to only finding out after upgrading and starting Visual Studio that you need to either uninstall and re-install your old version, or go through procurement to get a new licence and live without NCrunch in the interim.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  18. Enable "Build Configuration" to be set at the global level

    Hopefully the title of this is enough, but basically we have the following scenario:

    Some of our Grid Node servers are on premises and have a "local" SQL instance. This fits in well with our test config as they all point to the local instance.

    We also have some Grid Nodes running in Azure, and these do not have SQL Server installed but we'd like to point them to SQL Azure (so basically change the connection string).

    We can do this on a "Project Level" currently, but we'd like it to be configurable on a per machine level.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  19. make "First Time Crunch" Dialog for each new solution optional.

    I, and I'm sure others as well, use a similar, if not identical, NCrunch configuration for each solution. So I would suggest making the "First Time Crunch" dialog optional for new solutions. If disabled, a default configuration could be applied to each new solution.

    10 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  20. Support for Visual Studio 2015

    16 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  9 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
2
  • Don't see your idea?

Feature Requests

Categories

Feedback and Knowledge Base

(thinking…)