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

Notification

Icon
Error

PostSharp build problem
joelnet
#1 Posted : Thursday, April 12, 2012 6:07:09 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 4/12/2012(UTC)
Posts: 2

Was thanked: 1 time(s) in 1 post(s)
I just added PostSharp to the project and now NCrunch will not build the project. This is the error:

C:\Users\joelt\AppData\Local\NCrunch\4204\16\packages\PostSharp.2.1.6.13\tools\PostSharp.targets (222): The "PostSharp21MoveWithRetry" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "c:\Windows\Microsoft.NET\Framework\v4.0.30319" directory.

I tried playing around with the Additional files to include, but I couldn't get anything working.
Remco
#2 Posted : Thursday, April 12, 2012 8:34:47 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 961 times
Was thanked: 1291 time(s) in 1197 post(s)
Hi, thanks for posting!

It definitely looks to me like NCrunch is not aware of the postsharp build step binaries and is therefore not copying them into its workspace. You should be able to confirm this by right clicking on the failed build in the Tests Window, choosing Advanced->Browse to workspace and checking to see if the workspace contains all the postsharp files needed to build.

The 'Additional Files To Include' configuration setting would definitely be the thing to resolve such a problem. Make sure you add a full reference to your PostSharp tools relative to your project file (unless you're specifying the config at solution level, in which case this is your solution file). You may even want to take a step further and include ALL the packages for your solution in this configuration setting. At solution level, this would probably be something like:

packages\**.*

And at project level, it would probably be:

..\packages\**.*
1 user thanked Remco for this useful post.
DamonOverboe on 10/20/2014(UTC)
joelnet
#3 Posted : Thursday, April 12, 2012 10:22:22 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 4/12/2012(UTC)
Posts: 2

Was thanked: 1 time(s) in 1 post(s)
Fixed.

I didn't know I could add the whole packages directory. I also tried using *.* instead of **.*. I thought **.* was a typo. =)

Thanks!
1 user thanked joelnet for this useful post.
Remco on 4/13/2012(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.024 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download