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

Notification

Icon
Error
Unable to get NCrunch running due to absolute output paths
Options
Previous Topic Next Topic
Daniel Rose
#1 Posted : Friday, October 7, 2011 1:58:25 PM(UTC)
Rank: Member

Groups: Registered
Joined: 10/7/2011(UTC)
Posts: 29
Location: Aachen, Germany

Thanks: 6 times
Was thanked: 5 time(s) in 4 post(s)
My solution has an absolute output path (OutDir), since the output is on a different drive from the solution, m:\exaplus\bin. However, the NCrunch runner does not handle this case and simply appends this absolute path to the workspace. Thus, the built assembly is not found (and also not properly generated). As output text in the processing queue I get the following, for example:

ERROR (Compilation): Core: (0): Unable to find built assembly. Checked locations: C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\m:\exaplus\bin\Microsoft.WindowsAPICodePack.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\m:\exaplus\bin\Microsoft.WindowsAPICodePack.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\m:\exaplus\bin\Microsoft.WindowsAPICodePack.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\m:\exaplus\bin\Core.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\m:\exaplus\bin\Core.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\m:\exaplus\bin\Core.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\m:\exaplus\bin\Microsoft.WindowsAPICodePack.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\m:\exaplus\bin\Microsoft.WindowsAPICodePack.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\m:\exaplus\bin\Microsoft.WindowsAPICodePack.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\m:\exaplus\bin\Core.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\m:\exaplus\bin\Core.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\m:\exaplus\bin\Core.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\debug\Microsoft.WindowsAPICodePack.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\debug\Microsoft.WindowsAPICodePack.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\debug\Microsoft.WindowsAPICodePack.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\debug\Core.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\debug\Core.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\debug\Core.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\debug\Microsoft.WindowsAPICodePack.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\debug\Microsoft.WindowsAPICodePack.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\debug\Microsoft.WindowsAPICodePack.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\debug\Core.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\debug\Core.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\debug\Core.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\Microsoft.WindowsAPICodePack.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\Microsoft.WindowsAPICodePack.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\Microsoft.WindowsAPICodePack.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\Core.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\Core.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\bin\Core.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\Microsoft.WindowsAPICodePack.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\Microsoft.WindowsAPICodePack.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\Microsoft.WindowsAPICodePack.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\Core.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\Core.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\bin\Core.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\debug\Microsoft.WindowsAPICodePack.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\debug\Microsoft.WindowsAPICodePack.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\debug\Microsoft.WindowsAPICodePack.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\debug\Core.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\debug\Core.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\debug\Core.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\debug\Microsoft.WindowsAPICodePack.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\debug\Microsoft.WindowsAPICodePack.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\debug\Microsoft.WindowsAPICodePack.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\debug\Core.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\debug\Core.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\debug\Core.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\.\Microsoft.WindowsAPICodePack.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\.\Microsoft.WindowsAPICodePack.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\.\Microsoft.WindowsAPICodePack.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\.\Core.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\.\Core.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\WindowsAPI.Core\.\Core.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\.\Microsoft.WindowsAPICodePack.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\.\Microsoft.WindowsAPICodePack.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\.\Microsoft.WindowsAPICodePack.lib
C:\Users\rose\AppData\Local\NCrunch\8144\9\.\Core.dll
C:\Users\rose\AppData\Local\NCrunch\8144\9\.\Core.exe
C:\Users\rose\AppData\Local\NCrunch\8144\9\.\Core.lib
Back to top
WWW
Remco
#2 Posted : Saturday, October 8, 2011 10:07:10 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi Daniel -

Thanks for posting! Using an absolute output path isn't recommended as NCrunch needs to be able to build your solution without interference from other activities that may be going on in the output path (i.e. if you were running your application). My suggestion would be to change your project configuration so that the output path is using a relative reference when NCrunch builds the project. You can do this using the $(NCrunch) environment variable within MSBuild. For example:


<OutDir Condition=" '$(NCrunch)'=='1' ">bin</OutDir>
<OutDir Condition=" '$(NCrunch)'=='' ">m:\exaplus\bin</OutDir>

I hope this does the trick :)


Cheers,

Remco
Back to top
1 user thanked Remco for this useful post.
Daniel Rose on 3/30/2012(UTC)
Daniel Rose
#3 Posted : Monday, October 10, 2011 8:39:57 AM(UTC)
Rank: Member

Groups: Registered
Joined: 10/7/2011(UTC)
Posts: 29
Location: Aachen, Germany

Thanks: 6 times
Was thanked: 5 time(s) in 4 post(s)
Hi Remco,

That did the trick.

Thank you!
Back to top
WWW
1 user thanked Daniel Rose for this useful post.
Remco on 10/10/2011(UTC)
Users browsing this topic
Guest
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.044 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download