I went ahead and finished the change that I intended. StyleCop is disabled by default, but may be enabled from the command line. This paves the way for Jenkins builds. Developers—of course—can also enable StyleCop from the command line or run it from inside VS.

Best,
Dave

On May 1, 2014, at 7:47 PM, David Noble <dnoble@splunk.com<mailto:dnoble@splunk.com>> wrote:

I intended to disable StyleCop runs during builds on all platforms. In VS you can always run StyleCop by way of context menu. Once we've got Jenkins set up we'll enable StyleCop during builds on Jenkins. Those builds will always be done on Windows. There's no need for a platform check.

Sent from my iPhone

On May 1, 2014, at 7:40 PM, "Denis Gladkikh" <notifications@github.com<mailto:notifications@github.com>> wrote:


In examples/authenticate/authenticate.csproj:

> @@ -12,6 +12,7 @@
>      <TargetFrameworkVersion>v4.5</TargetFrameworkVersion>
>      <FileAlignment>512</FileAlignment>
>      <TargetFrameworkProfile />
> +    <StyleCopEnabled>False</StyleCopEnabled>


I guess you can try to optionally disable it only in xbuild project system (Xamarin) by Condition. But I don't know if Xamaron/MonoStudio/XBuild somehow can tell you if it is xamarin / not visual studio itself.

—
Reply to this email directly or view it on GitHub<https://github.com/splunk/splunk-sdk-csharp-pcl/pull/7/files#r12218103>.