Welcome Guest! To enable all features please Login or Register.



Azure Functions project causes a Console to be open every time NCrunch builds
#1 Posted : Tuesday, February 06, 2018 1:09:25 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 2/6/2018(UTC)
Posts: 1
Location: United Kingdom


I am having a very annoying issue whenever there is an Azure Functions project in my solution.

  • Visual Studio 2017 15.5.5
    Windows 7

In a solution with NCrunch enabled, create a new Azure Functions project. You will repeatedly see a cmd console being opened every time you make a change. The title of the console is "Microsoft.NET.Sdk.Functions.Generator.exe"

Current workaround:
Configure NCrunch to completely ignore the project, but this is far from ideal.

Were you aware of this issue? Is there a better workaround available?
#2 Posted : Tuesday, February 06, 2018 10:22:10 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 5,049

Thanks: 672 times
Was thanked: 797 time(s) in 758 post(s)
Hi, thanks for posting.

For a good number of years now, NCrunch hasn't contained any code that would instantiate a console window under windows. My guess would be that this is being triggered by a build step in your project that is creating the window in its own code. As such, the problem would be in your build system rather than NCrunch itself.

Unfortunately there isn't much I can do to help you with this problem. Azure projects aren't officially supported by NCrunch. I recommend looking to see if there are any updates to your Azure toolkit or whether there are any build steps you can safely disable using NCrunch-conditional build behaviour.

Edit: I've had an idea that may help. If the build system contains code that insists on creating a visible window, there isn't much NCrunch can do to stop it. However, it IS possible to set up your environment in such a way that the build code will run under a different user profile. You can do this using NCrunch's distributed processing. Basically, set up a grid node on your local machine, transfer all the local processing to it (disable (local) in the Grid Management Window), then set this node to run under a different user account on your machine. In this way, you'll never see the window appear unless you run a test with the debugger attached.
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.025 seconds.