Skip to main content

A command-line tool to clean Visual Studio generated folders (.vs, bin, obj)

Total Downloads
346
346
Published
Jun 6, 2025
1y ago

Get Started

dotnet add package VsCleanerTool --version 1.0.0

No framework information available.

README

VsCleanerTool

A .NET tool to clean up Visual Studio generated folders (.vs, bin, obj) from project directories.

For full documentation and updates, visit our project site.

Installation

Install as a global tool:

dotnet tool install --global VsCleanerTool

Or install locally to your project:

dotnet new tool-manifest # If you don't have one
dotnet tool install VsCleanerTool

Usage

Navigate to your project directory and run:

# Preview mode - shows what would be deleted
vsclean

# Delete mode - removes the folders
vsclean --delete
# or
vsclean -d

Features

  • Scans recursively from the current directory
  • Identifies .vs, bin, and obj folders
  • Preview mode shows which folders would be deleted
  • Delete mode removes the found folders
  • Checks if .vs folder is locked by Visual Studio
  • Color-coded output for better readability

Building from Source

git clone [repository-url]
cd VsCleanerTool
dotnet pack

This will create a NuGet package in the ./nupkg directory.

To install the locally built package:

dotnet tool install --global --add-source ./nupkg VsCleanerTool

License

MIT

Downloads by Version

Not enough data for chart

Similar & Alternative Packages

Hand-picked matching NuGet libraries based on tags & ecosystem

Depended On By

Find packages that declare this package as a dependency. NuGet does not provide a reverse-dependency endpoint, so candidates are checked on demand.

Adoption Assessment

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.