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

Notification

Icon
Error
Build error using PostSharp, extending OnExceptionAspect
Options
Previous Topic Next Topic
Atreyu
#1 Posted : Tuesday, August 13, 2013 11:55:41 AM(UTC)
Rank: Member

Groups: Registered
Joined: 1/11/2013(UTC)
Posts: 11
Location: Netherlands

Thanks: 3 times
Was thanked: 1 time(s) in 1 post(s)
Right now I receive the following error when attempting to build a project which creates a custom postSharp aspect.
The project builds normally when performed explicitly in visual studio or on my Teamcity buildserver.

NCrunch however does not build stating:
Quote:
Argument not specified for parameter 'validOn' of 'Public Sub New(validOn As PostSharp.Extensibility.MulticastTargets)'.


Code:
<Serializable()>
<MulticastAttributeUsage(PersistMetaData:=True)>
Public NotInheritable Class ExceptionLoggedAttribute
	Inherits OnExceptionAspect
...


The attribute 'MulticastAttributeUsage' does have a friend argument 'ValidOn' (notice the case change).

PostSharp has recently been updated, can this also be a caching issue for NCrunch? If so, where can I clear the cache for NCrunch?
Back to top
Remco
#2 Posted : Tuesday, August 13, 2013 9:51:30 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 964 times
Was thanked: 1296 time(s) in 1202 post(s)
Hi,

Thanks for sharing this issue. I'm afraid my knowledge of postsharp is fairly limited, but I'll do my best to try and help figure out where this is clashing. Are you making use of any features in the newly introduced PostSharp version?

I think the best plan is to try placing NCrunch in compatibility mode to see if this has any effect on the build. Being a post-build manipulation tool, PostSharp may be expecting a certain project or solution structure when it attempts to adjust your code after NCrunch has built it - and it's entirely possible that modifications in the new version have introduced new assumptions that don't hold true in the NCrunch environment. Using compatibility mode can help to bring the NCrunch build closer to that of a normal build, and may help us to deductively figure out where the problem is.

Don't worry about caching. Every time you restart the NCrunch engine, any kind of build caching or workspacing is thrown away. NCrunch will store code coverage and test results, but none of this will make any difference to the build process.
Back to top
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.023 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download