 for Marianna's that is actually entertaining right now. And I can't be watching a show for only one character when there's no way that character will consistently get 50% of the focus. 

I actually think that the only thing I personally feel weird about D&amp;D is that I feel like it paints the idea that people can just suddenly be attracted to plus sized people which for the most part isn't true.  Personally, I'm not attracted to plus sized people and I don't think of it as a big deal. Because I know some people are exclusively attracted to them. Or some people don't care either ways. Dennis just doesn't seem like that's his type but I'll support the pairing either way because it's not that deep.<filename>docs/vs-2015/code-quality/ca2211-non-constant-fields-should-not-be-visible.md
---
title: 'CA2211: nicht konstante Felder sollten nicht sichtbar sein | Microsoft-Dokumentation'
ms.date: 11/15/2016
ms.prod: visual-studio-dev14
ms.technology: vs-ide-code-analysis
ms.topic: reference
f1_keywords:
- CA2211
- NonConstantFieldsShouldNotBeVisible
helpviewer_keywords:
- NonConstantFieldsShouldNotBeVisible
- CA2211
ms.assetid: e1e42c40-0acd-4312-af29-70133739a304
caps.latest.revision: 15
author: jillre
ms.author: jillfra
manager: wpickett
ms.openlocfilehash: aa67c33eac5d618c0a080323720775beea7b68c3
ms.sourcegitcommit: 6cfffa72af599a9d667249caaaa411bb28ea69fd
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 09/02/2020
ms.locfileid: "85548212"
---
# <a name="ca2211-non-constant-fields-should-not-be-visible"></a>CA2211: Nicht konstante Felder sollten nicht sichtbar sein.
[!INCLUDE[vs2017banner](../includes/vs2017banner.md)]

|Element|value|
|-|-|
|TypName|NonConstantFieldsShouldNotBeVisible|
|CheckId|CA2211|
|Category|Microsoft. Usage|
|Unterbrechende Änderung|Breaking|

## <a name="cause"></a>Ursache
 Ein öffentliches oder geschütztes statisches Feld ist nicht konstant und ist nicht schreibgeschützt.

## <a name="rule-description"></a>Beschreibung der Regel
 Statische Felder, die weder konstant noch schreibgeschützt sind, sind nicht threadsicher. Der Zugriff auf ein solches Feld muss sorgfältig gesteuert werden und erfordert erweiterte Programmierverfahren für die Synchronisierung des Zugriffs auf das Klassenobjekt. Da es schwierig ist, die Kenntnisse zu erlernen und zu meistern, und das Testen eines solchen Objekts seine eigenen Herausforderungen darstellt, werden statische Felder am besten zum Speichern von Daten verwendet, die sich nicht ändern. Diese Regel gilt für Bibliotheken. Anwendungen sollten keine Felder verfügbar machen.

## <a name="how-to-fix-violations"></a>Behandeln von Verstößen
 Um einen Verstoß gegen diese Regel zu beheben, machen Sie das statische Feld konstant oder schreibgeschützt. Wenn dies nicht möglich ist, sollten Sie den Typ so umgestalten, dass er einen alternativen Mechanismus verwendet, wie z. b. eine Thread sichere Eigenschaft, die den Thread sicheren Zugriff auf das zugrunde liegende Feld verwaltet. Beachten Sie, dass Probleme, wie z. b. Sperr Konflikte und Deadlocks, die Leistung und das Verhalten der Bibliothek beeinflussen können.

## <a name="when-to-suppress-warnings"></a>Wann sollten Warnungen unterdrückt werden?
 Es ist sicher, eine Warnung aus dieser Regel zu unterdrücken, wenn Sie eine Anwendung entwickeln und daher die vollständige Kontrolle über den Zugriff auf den Typ haben, der das statische Feld enthält. Bibliotheks-Designer sollten eine Warnung aus dieser Regel nicht unterdrücken. durch die Verwendung nicht konstanter statischer Felder kann die Verwendung der Bibliothek für Entwickler schwierig werden.

## <a name="example"></a>Beispiel
 Das folgende Beispiel zeigt einen Typ, der gegen diese Regel verstößt.

 [!code-csharp[FxCop.Usage.AvoidStaticNonConstants#1](../snippets/csharp/VS_Snippets_CodeAnalysis/FxCop.Usage.AvoidStaticNonConstants/cs/FxCop.Usage.AvoidStaticNonConstants.cs#1)]
 [!code-vb[FxCop.Usage.AvoidStaticNonConstants#1](../snippets/visualbasic/VS_Snippets_CodeAnalysis/FxCop.Usage.AvoidStaticNonConstants/vb/FxCop.Usage.AvoidStaticNonConstants.vb#1)]
I am so sad about the fires. Many hikes I will never experience. I’m glad you got to St. John.
A beautiful read. So reminiscent of Mary Oliver. I can imagine the two of you would be good friends. Thank you for sharing this lovely week.
I would love to sit, in silence no doubt, with Mary Oliver. Thank you for reading.New Delhi, Sep 17: In a major blow to the Arvind Kejriwal-led Delhi government, the panel appointed by the Information and Broadcasting Ministry on Saturday ordered to “reimburse to the state exchequer” the entire amount that the Aam Aadmi Party had spent on its advertisements.
The panel charged the Delhi government of violating Supreme Court guidelines.
The committee on content regulation of government advertisements asserted that if any Chief Ministers want to promote their policies vital to the nation, then such political parties should bear the expenditure of such publicity and not the concerned government, an official here said.
The three-member committee was chaired by former Chief Election Commissioner B. B. Tandon and included Ogilvy and Mather India’s Piyush Pandey and journalist Rajat Sharma of India TV.
It further added that the AAP government should not have issued advertisements on incidents taking place in other states.
According to the Supreme Court order of May 13, 2015, advertisements by state governments should not be “outside its boundaries”, but it should be for attracting investment, business and talent to the state.
The Top court had also clarified that such advertisements should be designed accordingly for the purpose, and released for the specific target group, the panel said.
It also concluded that the AAP government should assess all expenditure made on advertorials — advertisement in the form of editorial content — mentioning AAP, along with those in which Chief Minister Arvind Kejriwal had tried to target the opposition.
The Information and Broadcasting ministry had in April formed the content regulation committee.
Today I just thought about showcasing/displaying my StackOverflow flair/badge in my LinkedIn profile. LinkedIn is a good place to show it because it’s a perfect match between your reputation as a software guy and possible good opportunities.
Since LinkedIn doesn’t allow one to put html code snippets in profile fields this showed to be a difficult task at first. Nothing that a little bit more thinking couldn’t solve: Google presentation application to the rescue.
Well, basically what you have to do is create a simple online Google Docs presentation. You could also create an Office PowerPoint presentation and upload it. For sure it’ll give you a lot more customization options. I’ve chosen Google presentation because it suffices my needs for the moment.
Just substitute my StackOverflow user id highlighted above by yours to get your flair.
To change the theme, add?theme=clean or?theme=dark or?theme=hotdog to the end of the image URL.
The bad point in this approach is that as your reputation grows your presentation won’t show your updated flair. You’ll have to open the presentation and re-add the flair image to reflect your current SO reputation.
Google should give us a way to have dynamic content inside a presentation (its spreadsheet service allows this kind of content). This is something that is really missing in presentations. Hey Google, can you hear me?
IS it possible to show SO flair on LinkedIn?
В этой