Skip to content

Update README.md #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
canderso wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -355,6 +355,26 @@ If the style is used only on a portion of the file:
- Make the style an explicit style,
- Add the proper style binding in all involved controls.

#### XA3003 - Name should reflect usage scenario
##### **Cause**
As the application evolves, styles tend to get used on controls and/or cases that weren’t necessarily thought of in the first place. Having style names reflecting their usage eases app maintenance.

##### **Rule description**
A violation of this rule occurs when a style is used for something else that it was initially meant for causing its name to be out of sync with its purpose. For example:

```xml
<Style x:Key="ListBoxStyle" TargetType="phone:LongListSelector" />
```

As soon as the use of a style is changed and/or extended it should be renamed to reflect its new use.

##### **How to fix violation**

Rename your style to reflect its use.

```xml
<Style x:Key=" LongListSelectorStyle" TargetType="phone:LongListSelector" />
```

### XA4x. Resource files organization

Expand Down