Hi, thanks for posting about these issues.

The postsharp problem is caused by a build dependency on a binary file that NCrunch isn't aware of. Right now NCrunch doesn't recognise the "UsingTask" MSBuild tag, so even though it is likely picking up the .targets import without problems, it isn't aware of everything that the .targets script needs in order to build your project. This should be very easy to fix. NCrunch has an 'Additional files to include' setting that you can use to tell it about special files that it hasn't been able to identify automatically. Adding the resource directory for postsharp to this setting (at project or solution level) should solve this problem.

The DevArt issue is one that I'm a little less clear on how to fix, though most likely NCrunch is following the same behaviour as your CI environment. My suspicion here is that the DevArt library is dynamically trying to find its license information, and for whatever reason this information is present in your normal development build environment, but it doesn't exist in the workspace that NCrunch is using to build your project. You can easily browse the contents of an NCrunch workspace by right-clicking on a project in the Tests Window and choosing the 'browse to workspace' option. Something that may help with this problem is turning on the 'Copy referenced assemblies to workspace' option for your tests project, as this may copy the DevArt dependencies in automatically. Otherwise, it may be worth looking at adding a custom build step that specifically copies the license file into your output directory (this will probably fix your CI environment too).