$ show BornToBeRoot/NETworkManager
NETworkManager is a comprehensive Windows-based network administration and troubleshooting tool built with WPF and the MVVM pattern. It provides an integrated suite of network utilities including remote access (RDP, PowerShell, PuTTY, TigerVNC, WebConsole), network diagnostics (WiFi scanner, IP/port scanners, ping monitor, traceroute, DNS lookup), configuration tools (firewall, hosts file editor), and various network utilities (subnet calculator, bit calculator, OUI/port lookup, RDAP/Whois, IP geolocation). The application features a tabbed interface where each tool operates as a separate tab, profile-based configuration management for saving host/group settings, settings persistence with system-wide policy support, localization for 16+ languages, and data export capabilities (CSV, XML, JSON). The architecture follows clean separation of concerns with dedicated projects for Controls, Converters, Models, Profiles, Settings, Utilities, and ViewModels/View pairs.
The LLM identified 5 files worth highlighting for reuse:
A simple WPF IValueConverter that converts boolean values to Visibility.Collapsed or Visibility.Visible. It is isolated, has no internal dependencies, and is reusable in any WPF application for visibility binding.
A static helper class for parsing host specifications, including IP addresses, hostnames, and ranges (e.g., '192.168.1.1-10', 'example.com'). It is self-contained, uses only .NET framework types, and provides a non-obvious utility for network applications.
Provides extension methods for ObservableCollection to manage history lists with automatic size limiting (e.g., AddWithLimit). It is isolated, reusable, and demonstrates a common pattern for maintaining bounded collections in MVVM applications.
A standard implementation of ICommand for MVVM applications, allowing ViewModels to expose commands for UI binding. It is lightweight, has no internal dependencies, and is a foundational component for WPF MVVM.
A simple event aggregator (publish-subscribe) that enables loose coupling between components. It is self-contained, has no external dependencies beyond .NET, and is reusable in any .NET application for communication between ViewModels or services.