C#intermediatedevopsAI generated

File Integrity Monitor Windows Service

A background service that watches a set of directories using FileSystemWatcher, computes and stores file hashes, and alerts via log/event when files are unexpectedly modified, added, or deleted, packaged as a Windows Service. Learners practice FileSystemWatcher events, hashing, and Windows Service hosting in .NET.

Estimate
~10h
Steps
6
Completed by
0
Proposed by
codeseed.app

FileSystemWatcher · .NET Worker Service · SHA256

Project roadmap

  1. 01

    Build the baseline hash snapshot

    ~1.5h

    Walk watched directories and compute SHA256 hashes for all files, storing them as a baseline.

  2. 02

    Set up FileSystemWatcher event handlers

    ~2h

    Wire up Created, Changed, Deleted, and Renamed events for the watched directories.

  3. 03

    Implement change verification against baseline

    ~2h

    On each event, recompute the file's hash and compare against the baseline to confirm a real content change.

  4. 04

    Add structured logging of integrity events

    ~1.5h

    Log each detected change with timestamp, path, and change type to a rolling log file.

  5. 05

    Package as a Worker Service / Windows Service

    ~2h

    Configure the app as a .NET Worker Service that can be installed and run as a Windows Service.

  6. 06

    Add configuration for watched paths

    ~1h

    Support an appsettings.json list of directories and exclude patterns to monitor.

Resources

Ready to build this?

Get a GitHub repo and start building. Your AI reviewer checks each step as you go.

~10h · 6 steps

Tech stack

FileSystemWatcher.NET Worker ServiceSHA256