visual studio 2017 - Project's StyleCop.Analyzers Ruleset appears in other solutions -


we trying create custom ruleset our company based on default ones microsoft, of more contentious ones disabled. works fine. stylecop.analysers works great, , warnings , errors created appropriately. works on our build server.

however... ruleset add projecta in solution1 listed in droplist of rulesets projectb in solution2. problem. if select ruleset, work locally when check in nobody else have same path. want deliver these rulesets nuget, company rulesets have same name , indistinguishable each other. if mean to, it's hard find right 1 in current solution.

this sucks, , cannot believe it's intended mode of operation. have missed? there flag in ruleset makes locally scoped rather machine-wide? microsoft support creating rulsets within project, why available in unrelated solutions?

do need work around , install them once vs extension? seems ridiculously complicated text file. bug in vs2017?

any pointers appreciated

-- update --

i can install rulset's here:

"c:\program files (x86)\microsoft visual studio\2017\enterprise\team tools\static analysis tools\rule sets"

they picked vs2017. that's great, if try build on build server won't have files, plus people's machines may have different versions. total mess.

i need able add ruleset solution , use within solution - no-further.

-- further update --

looks it's editor flakey. if load ruleset up, adds internal list maintains. whenever go droplist of available rulesets, shows ones it's seen still available.

so (unless knows better), seem process broken atm in vs2017. workaround add namespace of project nuget package getting deployed in ruleset name. doesn't stop duplication in droplists, means can tell difference , pick right copy of ruleset.

how transform rulset on nuget install? add ".pp" end of filename, , file parsed placeholders. in case "test.ruleset.pp" file have node thus:

<ruleset name="$rootnamespace$ recommended debug ruleset" description=" " toolsversion="15.0"> 

yes rather verbose names goes, go complain @ microsoft ruleset process broken.

other placeholders can found here: https://msdn.microsoft.com/library/vslangproj.projectproperties_properties.aspx


Comments

Popular posts from this blog

php - Vagrant up error - Uncaught Reflection Exception: Class DOMDocument does not exist -

vue.js - Create hooks for automated testing -

Add new key value to json node in java -