-----
**Warning: this wiki page is auto-generated by the Arnolyzer solution-build process. Do not directly edit this page, as your changes will be lost on the next commit.** To edit this page, please refer to [Contributing to this project](https://github.com/DavidArno/Arnolyzer/wiki/Contributing.md).

These wiki pages reflect the state of the project in development, per the last commit. For details of the latest release of the Arnolyzer Analysers, please see the [Arnolyzer website](http://http://davidarno.github.io/Arnolyzer/). 

-----
# AA1200 - Avoid Using Static Fields #
**Report code: AA1200-AvoidUsingStaticFields**

## Summary ##
<table>
<tr>
  <td><strong>Status</strong></td>
  <td>Implemented</td>
</tr>
<tr>
  <td><strong>Description</strong></td>
  <td>Static fields introduce global state and so should be avoided</td>
</tr>
<tr>
  <td><strong>Category</strong></td>
  <td><a href="GlobalStateAnalyzers.md">Global State Analyzers</a></td>
</tr>
<tr>
  <td><strong>Enabled by default:</strong></td>
  <td>Yes</td>
</tr>
<tr>
  <td><strong>Severity:</strong></td>
  <td>Error</td>
</tr>
</table>

## Cause ##



## How to fix violations ##

There currently aren't any implemented code-fixes for this rule.

## How to suppress violations ##

This rule can be suppressed using the following attributes: 

**[GlobalState]**<br/>A field or property annotated with GlobalState attribute is allowed to be static as it is explicitly declaring its need to be "globally" accessible.