BADF00D / DisposableFixer

This is a Visual Studio Extension and NuGet package that should identify and fix problems as memleaks while using IDisposables.

BADF00D/DisposableFixer Issues

newbie. cant seem to get it working.
Updated 4 months ago
Will this be updated for Visual Studio 2022?
Updated 2 years ago2
Add support for IAsyncLifetime
Updated 2 years ago
Add System.Net.Http.StreamContext as tracking Disposable
Updated 3 years ago
Add ContextDisposable to tracking types
Updated 3 years ago
Indisposed is correct spelling
Updated 3 years ago
Add support for IAsyncDisposable
Updated 4 years ago2
If Dispose(bool) is implemented, CodeFix with Dispose should not be offered
Updated 4 years ago
No code fix for Using declarations
Closed 4 years ago2
Add support for tuple syntax
Updated 4 years ago
Add standard IEnumerable Extension methods to ignore list
Updated 4 years ago
Added RX Multicast to tracking methods.
Closed 4 years ago1
Dispose as delegate
Closed 4 years ago1
Add CodeFix to add Disposable to Dispose* method
Updated 4 years ago
Add CodeFix that adds IDisposable tov ia AddTo to existing CompositDisposable
Updated 4 years ago
Using expression syntax for method declarations doesnt notify of undisposed object
Closed 4 years ago2
UndisposedFieldCodeFixProvider crashes
Updated 5 years ago
Add support to detect hidden disposable in async code
Closed 5 years ago
Field/Property assigned via await is not detected when field/property is only an IDisposable
Updated 5 years ago3
Fix warning on nuget packages
Updated 5 years ago
Add support for C#8 using declaration
Closed 5 years ago1
Switch to .Net Standard 2.0 and update to latest analyzer version
Closed 5 years ago1
Add support for System.Reactive.Disposables
Closed 5 years ago
Assigning an IDisposable to anothers class property should yield an warning
Closed 5 years ago1
When informing about undisposed non static or static members, their name should be part of the message
Closed 5 years ago
Add support for ReactiveProperty SetValidateNotifyError
Closed 5 years ago
When informing about undisposed local variables, their name should be part of the message
Closed 5 years ago4
Crash on Quick Actions menu call
Closed 5 years ago3
Conditional object creation without Using statement incorrectly warns
Closed 5 years ago
Crash on Quick Actions menu call
Closed 5 years ago
Crash on context menu call
Closed 5 years ago1
Tokens not replaced in: DF0100 C# {0} implements IDisposable but return value {1} does not.
Closed 5 years ago4
Return values in Local method should be ignored
Closed 5 years ago
Dispose after last usage introduces error
Closed 5 years ago
Add warning if return type hides IDisposable interface
Closed 5 years ago
Intruduce Field and Dispose in dispose method crashes
Closed 5 years ago1
Receive LocalVariableNotDiposed when field is not disposed
Closed 5 years ago1
Using a tracking type/tracking method to dispose fields/properties initialized in constructor leads to a warning
Closed 5 years ago2
An anonymous undisposed variable is not marked as not disposed
Closed 5 years ago
Incorrect DF0021: request to dispose of a static variable
Closed 5 years ago6
Using an extension method to wrap CompositeDisposable.Add() triggers warning when it shouldnt
Closed 5 years ago2
Properties that are factories should get their own diagnostic ids
Closed 5 years ago1
Suggestion: Allow code marking to be disabled/less intrusive
Updated 5 years ago5
conditional in Using statement incorrectly warns
Closed 5 years ago2
Unexpected DF0001 when yield returning a disposable
Closed 5 years ago2
CancellationTokenRegistration should be ignored or should be not warnung
Closed 5 years ago1
Wrap in using does nothing
Closed 5 years ago
Wrap in using does not work correctly
Closed 5 years ago
Add support for Interlocked.Exchange
Closed 5 years ago2
Add some shields to show projects status
Closed 5 years ago