Good evening,
I wanted to give the latest version of NCrunch a try against one of my current projects and this project utilizes Microsoft's Application Insights and the later is using ETW under the hood.. and that in turn adds a new build target/post-build process to the project file(s) it is referenced in.. and even though regular building, manual unit testing etc all work fine, NCrunch fails to build these projects due to that post-build step with a rather strange error (exit code is 9930 or 9309 as far as I remember).
Basically you can reproduce this rather easily by creating a new solution/project, reference the MS EventSource NuGet package above, create a second Unit Test project that references the first project and try to run NCrunch on that solution.
What could I do in that case to use NCrunch nevertheless?
Cheers and thanks,
-Joerg
Remco NCrunch Developer
#6153
16 Jul 2014 23:42 UTC
Hi Joerg,
Thanks for sharing this issue.
Do you notice any difference in behaviour if you set NCrunch into compatibility mode for this solution?
Cheers,
Remco
Thanks for sharing this issue.
Do you notice any difference in behaviour if you set NCrunch into compatibility mode for this solution?
Cheers,
Remco
Good evening Remco,
I just set the options according to the compatibility mode instructions and still get the same build error. The output is the following:
NCrunch: If you are experiencing problems in getting this project to build, have a look at http://www.ncrunch.net/documentation/troubleshooting_project-build-issues
..\packages\Microsoft.Diagnostics.Tracing.EventRegister.1.0.24\build\Microsoft.Diagnostics.Tracing.EventRegister.targets (132): The command ""C:\Users\joerg\AppData\Local\NCrunch\9148\18\MyProject\packages\Microsoft.Diagnostics.Tracing.EventRegister.1.0.24\build\eventRegister.exe" -DumpRegDlls @"C:\Users\joerg\AppData\Local\NCrunch\9148\18\MyProject\MyProject.Backend.Logging\bin\Debug\MyProject.Backend.Logging.eventRegister.rsp" "C:\Users\joerg\AppData\Local\NCrunch\9148\18\MyProject\MyProject.Backend.Logging\bin\Debug\MyProject.Backend.Logging.dll" " exited with code 9009.
I've made a simple repro solution & uploaded it at: https://db.tt/XxnItRSN
Hope that helps!
-Joerg
I just set the options according to the compatibility mode instructions and still get the same build error. The output is the following:
NCrunch: If you are experiencing problems in getting this project to build, have a look at http://www.ncrunch.net/documentation/troubleshooting_project-build-issues
..\packages\Microsoft.Diagnostics.Tracing.EventRegister.1.0.24\build\Microsoft.Diagnostics.Tracing.EventRegister.targets (132): The command ""C:\Users\joerg\AppData\Local\NCrunch\9148\18\MyProject\packages\Microsoft.Diagnostics.Tracing.EventRegister.1.0.24\build\eventRegister.exe" -DumpRegDlls @"C:\Users\joerg\AppData\Local\NCrunch\9148\18\MyProject\MyProject.Backend.Logging\bin\Debug\MyProject.Backend.Logging.eventRegister.rsp" "C:\Users\joerg\AppData\Local\NCrunch\9148\18\MyProject\MyProject.Backend.Logging\bin\Debug\MyProject.Backend.Logging.dll" " exited with code 9009.
I've made a simple repro solution & uploaded it at: https://db.tt/XxnItRSN
Hope that helps!
-Joerg
Remco NCrunch Developer
#6162
17 Jul 2014 23:03 UTC
Hi Joerg,
Thanks for the code sample. This was a huge help.
I was able to make this project build by adding the following to the 'Additional files to include' project-level configuration setting for the failing project:
..\packages\Microsoft.Diagnostics.Tracing.EventRegister.1.0.26\build\**.*
It seems that the project has additional implicit dependencies that NCrunch wasn't able to automatically identify.
I hope this does the trick for you.
Cheers,
Remco
Thanks for the code sample. This was a huge help.
I was able to make this project build by adding the following to the 'Additional files to include' project-level configuration setting for the failing project:
..\packages\Microsoft.Diagnostics.Tracing.EventRegister.1.0.26\build\**.*
It seems that the project has additional implicit dependencies that NCrunch wasn't able to automatically identify.
I hope this does the trick for you.
Cheers,
Remco
That worked, thanks!
Is there any chance this kind of project(s) might be supported natively in the future? basically whenever such references change, I'll have to manually adjust the paths which is pretty much time wasted / potentially forgotten etc..
Cheers,
-Jörg
Is there any chance this kind of project(s) might be supported natively in the future? basically whenever such references change, I'll have to manually adjust the paths which is pretty much time wasted / potentially forgotten etc..
Cheers,
-Jörg
Remco NCrunch Developer
#6166
19 Jul 2014 23:07 UTC
Great to hear!
It's difficult for NCrunch to automatically resolve all dependencies of packages like this. The problem is that the dependencies aren't always referenced in a manner that can be consistently analysed. The 'Additional files to include' is the default way to solve problems with implicit references such as this.
NCrunch does actually support more complex expressions inside the additional files to include. For example, you should also be able to specify: ..\packages\Microsoft.Diagnostics.Tracing.EventRegister*\build\**.*
However, the validation on the configuration control seems to throw this out. To make use of it, you'll need to edit the .v2.ncrunchproject file directly and specify the config setting yourself. I'll see about getting the validation fixed.
Cheers,
Remco
It's difficult for NCrunch to automatically resolve all dependencies of packages like this. The problem is that the dependencies aren't always referenced in a manner that can be consistently analysed. The 'Additional files to include' is the default way to solve problems with implicit references such as this.
NCrunch does actually support more complex expressions inside the additional files to include. For example, you should also be able to specify: ..\packages\Microsoft.Diagnostics.Tracing.EventRegister*\build\**.*
However, the validation on the configuration control seems to throw this out. To make use of it, you'll need to edit the .v2.ncrunchproject file directly and specify the config setting yourself. I'll see about getting the validation fixed.
Cheers,
Remco
Remco wrote:Great to hear!
NCrunch does actually support more complex expressions inside the additional files to include. For example, you should also be able to specify: ..\packages\Microsoft.Diagnostics.Tracing.EventRegister*\build\**.*
Ahhh with that I can be perfectly happy with :) If you ever come by that control and do manage to let it keep these (now manually entered) expressions, it would be highly appreciated.
Nevertheless I did purchase a license for myself and really, really like it.
Thanks Remco & have a great Sunday!
-Jörg
Post a reply
Log in to reply.