FYI -
It appears you guys are missing [EngineDependency
(typeof(SuppressMessageEngine))] on all of your compiled rules.
I see that the tests manually add the engine via
Runner.Engines.Subscribe
("Gendarme.Framework.Engines.SuppressMessageEngine") -- but that in
the real runner, EngineDependencyAttribute is reflected on for each
rule to determine whether to add it to the runner. Since there are no
such attributes applied anywhere, the engine is never added /
FxCopCompatibility attributes are ignored, etc.
As a workaround, I *think* I can create a quicky and dirty hack rule
just to enable SuppressMessageEngine.
Am I missing anything / is there an alternate approach to enabling
this engine? Or was this left out intentionally?
--
You received this message because you are subscribed to the Google Groups
"Gendarme" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/gendarme?hl=en.
