Multiple Warnings from 'StyleCopTask' task

[ryzngard]

When pulling and building the source, I have multiple of the below error.

Severity	Code	Description	Project	File	Line	Suppression State
Error		The "StyleCopTask" task could not be loaded from the assembly C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild..\StyleCop 4.7\StyleCop.dll. Could not load file or assembly 'file:///C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\StyleCop 4.7\StyleCop.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.	XboxWdpDriver	C:\Program Files (x86)\MSBuild\StyleCop\v4.7\StyleCop.targets	98	Error

Full build log below from re-build build.txt

[hpsin]

@WilliamsJason - is there a way to make stylecop optional in this project? I believe it's optional for the rest of the solution.

@ryzngard - this should just work, we point to the StyleCop via the registry, can you check this key? HKLM\Software\CodePlex\StyleCop TargetsDir ? Looks like it's finding your Enterprise install of VS 2017 and then not finding Stylecop. Might just have to install it.

[WilliamsJason]

I thought we'd made it optional :/

@MattHyman was mentioning you can add StyleCop as a NuGet dependency. We should switch to that, it should avoid forcing people to manually install it (or not install it and miss warnings that we should be fixing).

[MattHyman]

I tried the nuget version, at least for me it did not work with the UWP projects. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Jason Williams <notifications@github.com> Sent: Thursday, November 30, 2017 10:21:33 AM To: Microsoft/WindowsDevicePortalWrapper Cc: Matt Hyman; Mention Subject: Re: [Microsoft/WindowsDevicePortalWrapper] Multiple Warnings from 'StyleCopTask' task (#277) I thought we'd made it optional :/ @MattHyman<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmatthyman&data=02%7C01%7Cmathy%40microsoft.com%7Cf291764b3e734f066afb08d5381f3236%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636476628993791881&sdata=%2F3f7JmbITITVtFzO9wbr55jywGrcr8EUd6eRjm%2FNuJA%3D&reserved=0> was mentioning you can add StyleCop as a NuGet dependency. We should switch to that, it should avoid forcing people to manually install it (or not install it and miss warnings that we should be fixing). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FWindowsDevicePortalWrapper%2Fissues%2F277%23issuecomment-348275783&data=02%7C01%7Cmathy%40microsoft.com%7Cf291764b3e734f066afb08d5381f3236%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636476628993791881&sdata=JFqwqnYtlfXvV1CAZab6gNYIRWAG%2BGm2O642Cj%2FyuPk%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABc0Y1sZVrbTX-Nsz5mgDo_8u5ykMNdVks5s7vItgaJpZM4Qk28a&data=02%7C01%7Cmathy%40microsoft.com%7Cf291764b3e734f066afb08d5381f3236%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636476628993791881&sdata=s9P10CWiu2KK5fFnGyDVQ9v%2Fy01RMn2OgekGQ2u378k%3D&reserved=0>.

[WilliamsJason]

I'm going to turn off StyleCop build integration. Maybe we can eventually sort out the NuGet package but for now everyone running StyleCop will need to run it via 'Tools->Run StyleCop' since the build integration seems to be having issues when StyleCop is installed.