RuleVault

Business-rule discovery for Visual Studio.

RuleVault analyzes legacy source code and documentation to surface potential business rules for human review — discover, review, decide, and preserve them without ever leaving Visual Studio.

What RuleVault Does

RuleVault brings scanning, review, decision-making, and preservation of business rules into a native Visual Studio tool window — the RuleVault Developers Console. Point it at a solution, file, or folder, and RuleVault scans the source for candidate business rules hidden in code and documentation, so your team can confirm and preserve institutional knowledge before it's lost.

Supported Sources

C#
VB.NET
Java
COBOL
SQL stored procedures
Oracle PL/SQL
Configuration files
Documentation

Developer Workflow

Scan — Scan a solution, individual file, or folder.
Review — Inspect discovered findings and their supporting details.
Navigate — Open the related source location directly from a finding.
Decide — Record a review decision for each finding.
Preserve — Save approved business-rule information to the RuleVault repository.
Export — Export findings to CSV for downstream reporting or analysis.

Key Features

Native Visual Studio tool-window experience.
Solution, file, and folder scanning.
Summary counts for Business Rules, Possible Rules, Exclusions, and Files Scanned.
Finding review with decision capture.
Source navigation from a finding straight back to the related code.
CSV export for downstream review and reporting.
Database connection status, retry, and copyable diagnostic messages.
Automatic creation of the RuleVaultDB database and required tables on first successful connection.

Requirements

Visual Studio 2022, version 17.14 or later (Community, Professional, or Enterprise).
A reachable Microsoft SQL Server instance. RuleVault provisions the RuleVaultDB database and its tables automatically after connecting — the database name must be RuleVaultDB.

Getting Started

Install RuleVault from the Visual Studio Marketplace (or a downloaded .vsix).
In Tools > Options, find RuleVault and set the SQL Server connection string (database name must be RuleVaultDB).
Open Tools > RuleVault to launch the RuleVault Developers Console.
RuleVault connects and prepares RuleVaultDB automatically — use Retry if the connection needs a moment.
Start with Scan Solution, Scan File, or Scan Folder.

Troubleshooting

If the tool window shows a connection error: confirm the SQL Server instance and connection string in Tools > Options are correct, then press Retry. Hover over the error message for the full diagnostic text, or use Copy to place it on the clipboard for support.

Support

Software Factories of America https://www.SoftwareFactoriesOfAmerica.com