search
Found 10 packages
JetBrains.Annotations✓
JetBrains.Annotations help reduce false positive warnings, explicitly declare purity and nullability in your code, deal with implicit usages of members, support special semantics of APIs in ASP.NET and XAML frameworks and otherwise increase accuracy of JetBrains Rider and ReSharper code inspections.
v2025.2.4
↙ 413.1M / total
jetbrainsresharperriderannotationscanbenull
JetBrains.Annotations.Sources✓
JetBrains.Annotations help reduce false positive warnings, explicitly declare purity and nullability in your code, deal with implicit usages of members, support special semantics of APIs in ASP.NET and XAML frameworks and otherwise increase accuracy of JetBrains Rider and ReSharper code inspections.
v2025.2.4
↙ 159.3K / total
jetbrainsresharperriderannotationscanbenull
pkg
JetBrains.Annotations.Portable
ReSharper Annotations help reduce false positive warnings, explicitly declare purity and nullability in your code, deal with implicit usages of members, support special semantics of APIs in ASP.NET and XAML frameworks and otherwise increase accuracy of ReSharper code inspections. This package is a clone of the JetBrains.Annotations project by JetBrains, but not resulting in a public .dll that could prove to collide with other implementations, but resulting in an internal code contribution that will not collide externally. For some reason the Nuget team decided that the content files feature is not (yet) available for .net Core projects. In this situation you might want to consider downloading the actual code file. See https://github.com/bepost/jetbrains-annotations-internal for more information. All credits for the actual functionality go to the JetBrains team.
v10.2.3
↙ 209.4K / total
jetbrainsresharperannotationscanbenullnotnull
pkg
ResharperCodeContractNullability
Reports diagnostics, helping you to annotate your source tree with (Item)NotNull / (Item)CanBeNull attributes. See also: https://www.jetbrains.com/resharper/help/Code_Analysis__Code_Annotations.html You need Visual Studio 2015/2017/2019 and Resharper v9 or higher to use this analyzer. See package "ResharperCodeContractNullabilityFxCop" if you use Visual Studio 2013 or lower.
v2.0.2
↙ 63.1K / total
resharpercodecontractsannotationsnullability
pkg
NullCheckAnalyzer
This package is for projects on Microsoft Visual Studio 2015 to have design-time and compile-time warnings. It checks, that all reference parameters in methods and constructors have NotNull/CanBeNull attributes. You have to use Jetbrains.
v1.0.0.3
↙ 14.3K / total
NullCheckAnalyzeranalyzersRoslynResharperNotNull
pkg
ResharperCodeContractNullabilityFxCop
Reports diagnostics, helping you to annotate your source tree with (Item)NotNull / (Item)CanBeNull attributes. See also: https://www.jetbrains.com/resharper/help/Code_Analysis__Code_Annotations.html You need Visual Studio 2013/2012/2010 and Resharper v8 or higher to use this analyzer. See package "ResharperCodeContractNullability" if you use Visual Studio 2015.
v1.0.3
↙ 10.7K / total
resharpercodecontractsannotationsnullability
ReSharper.Annotations.WindowsCE
ReSharper Annotations help reduce false positive warnings, explicitly declare purity and nullability in your code, deal with implicit usages of members, support special semantics of APIs in ASP.NET and XAML frameworks and otherwise increase accuracy of ReSharper code inspections. All usages of ReSharper Annotations attributes are erased from metadata by default, which means no actual binary reference to 'JetBrains.Annotations.dll' assembly is produced. If you need to preserve these attributes in metadata, just define 'JETBRAINS_ANNOTATIONS' conditional compilation symbol in your projects.
v11.1.1
↙ 3.6K / total
jetbrainsresharperannotationscanbenullnotnull
pkg
Resharper.Annotations.Sources
A source code package of ReSharper annotations that help reduce false positive warnings, explicitly declare purity and nullability in your code, deal with implicit usages of members, support special semantics of APIs in ASP.NET and XAML frameworks and otherwise increase accuracy of ReSharper code inspections. The attributes NotNull and Pure are disabled by default, to enable it use NOTNULLATTRIBUTE_ENABLE and PUREATTRIBUTE_ENABLE respectively.
v2020.2.3
↙ 3.2K / total
sourcecompiletimejetbrainsattributescanbenull
pkg
CallMeMaybe
Provides a class and a few extension methods to facilitate common operations with values that may or may not exist. Traditionally, programmers often use `null` references to represent values that "aren't there", but the problem is that this was never their intended purpose. - Languages like C# don't provide a way to differentiate between reference variables that can be null and those that are guaranteed not to be. - The inventor of null references has [apologized](http://en.wikipedia.org/wiki/Tony_Hoare#Quotations) for creating them in the first place, calling them his "billion-dollar mistake." - This misuse of null references has spread far and wide, leading to the unfortunately-named `Nullable<>` type (which, being a value type, is never actually null), and attributes like `[CanBeNull]` and `[NotNull]` to help programmers know when they can expect a method to treat a null value as legitimate input. All this leaves us in a position where our best hope of avoiding `NullReferenceException`s lies in trying to make sure that our reference variables are *never* null. But in that case, how do we indicate when a value is *optional*? Well, that's where `Maybe<>` comes in.
v0.7.1
↙ 48.8K / total
maybemonadoptionoptional
Twia.ReSharper
This package contains the JetBrains.Resharper assembly with the annotations from the ReSharper Annotated Framework. The annotations are for use in combination with JetBrains ReSharper. See the project URL on how to use the annotations. The annotations are taken from ReSharper 9. Source code can be annotated with the shared annotations between the two versions such as [NotNull] and [CanBeNull], and can be double annotated with the [AssertionMethod] for ReSharper 6 and 9 and the [ContractAnnotation] for ReSharper 7 and above. As of ReSharper 9 the annotation attributes are all marked with the [Conditional("JETBRAINS_ANNOTATIONS")] attribute. As a result, by default the annotations do not end up in the metadata of the compiled assembly, and no reference is added to the JetBrains.Annotations assembly. To keep the annotations in the output, define the 'JETBRAINS_ANNOTATIONS' conditional compilation symbol in your project. JetBrains provides the NuGet package with ID JetBrains.Annotations (https://www.nuget.org/packages/JetBrains.Annotations/) which contains the same annotations, and should be considered as a good alternative to this package. Both packages only differ in the targets they provide builds for. The Twia.ReSharper package provides builds for .NET 2.0 (net20) and .NET 4.0 (net40). The JetBrans.Annotations package provides a .NET 2.0 (net20) and a few portable library builds. Finally, I have no links to JetBrains what so ever, except that I am a happy user of ReSharper.
v9.0.0
↙ 58.3K / total
resharperannotationsjetbrainstwia