Release 3.0.11

.gitignore

@@ -36,3 +36,5 @@ _UpgradeReport_Files/
 AppPackages/
 BundleArtifacts/
 /src/UI/WinUI (Package)/WinUI (Package).assets.cache
+
+.claude

OSDP-Bench.sln

@@ -24,6 +24,12 @@ Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "Windows", "src\UI\Windows\W
 EndProject
 Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "Core", "src\Core\Core.csproj", "{79C7EB0F-A75B-4DA7-BDDF-12C9714B48DF}"
 EndProject
+Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Docs", "Docs", "{ED2EC291-3353-442C-AD2C-3D3438798EF0}"
+	ProjectSection(SolutionItems) = preProject
+		README.md = README.md
+		docs\CLAUDE.md = docs\CLAUDE.md
+	EndProjectSection
+EndProject
 Global
 	GlobalSection(SolutionConfigurationPlatforms) = preSolution
 		Debug|Any CPU = Debug|Any CPU

README.md

@@ -1,8 +1,97 @@
-# OSDP Bench #
-Tool for configuring and troubleshooting OSDP devices.
+# OSDP Bench
 
-Phyisical access to spaces is typically granted using readers and badges. The readers are usually low powered end point devices that depends on a control panel to determine if the card credential is authroized to gain access. The communication between the reader and control panel is done via the Open Supervised Device Protocol (OSDP). Current access control panels can lack good tools to manage their connected OSDP devices. The goal of this project is to fill this gap with the necessary tools needed for technicians who are working with OSDP.
+A professional tool for configuring and troubleshooting OSDP devices.
 
-Core functionality is under an open source license to help increase the adoption rate of OSDP. A fully functional OSDP Bench tool can be compiled under this license at no cost. We encourage OSDP hardware vendors to utilize this project to accelerate the development of thier own OSDP releated tools.
+[![.NET](https://img.shields.io/badge/.NET-8.0-blue)](https://dotnet.microsoft.com/)
+[![License](https://img.shields.io/badge/License-Apache%202.0-green.svg)](LICENSE)
+[![Platform](https://img.shields.io/badge/Platform-Windows-lightgrey)](https://docs.microsoft.com/en-us/windows/)
 
-Contact [Z-bit Systems, LLC](https://z-bitco.com) for inquires regarding this project.
+## About
+
+Physical access to spaces is typically granted using readers and badges. The readers are usually low-powered end point devices that depend on a control panel to determine if the card credential is authorized to gain access. The communication between the reader and control panel is done via the Open Supervised Device Protocol (OSDP). Current access control panels can lack good tools to manage their connected OSDP devices. The goal of this project is to fill this gap with the necessary tools needed for technicians who are working with OSDP.
+
+Core functionality is under an open source license to help increase the adoption rate of OSDP. A fully functional OSDP Bench tool can be compiled under this license at no cost. We encourage OSDP hardware vendors to utilize this project to speed up the development of their own OSDP related tools.
+
+## Features
+
+- **Device Discovery** - Automatically discover OSDP devices on serial connections
+- **Real-time Monitoring** - Monitor card reads, keypad entries, and device status
+- **Device Configuration** - Configure LEDs, buzzers, and communication parameters
+- **Packet Tracing** - View detailed OSDP communication packets
+- **Multi-language Support** - Available in multiple languages
+- **Cross-platform** - Built on .NET 8.0 for modern compatibility
+
+## Getting Started
+
+### Prerequisites
+
+- .NET 8.0 SDK or later
+- Windows 10/11 (for WinUI version)
+- Serial port access for device communication
+
+### Installation
+
+1. Clone the repository:
+   ```bash
+   git clone https://github.com/bytedreamer/OSDP-Bench.git
+   cd OSDP-Bench
+   ```
+
+2. Build the solution:
+   ```bash
+   dotnet build OSDP-Bench.sln
+   ```
+
+3. Run the application:
+   ```bash
+   dotnet run --project src/UI/Windows
+   ```
+
+### Quick Start
+
+1. Launch OSDP Bench
+2. Select your serial port from the dropdown
+3. Choose "Discover" to automatically find devices or "Manual" to connect directly
+4. Begin monitoring device activity or configure device settings
+
+## Documentation
+
+### Project Documentation
+- **[Developer Guidelines](docs/CLAUDE.md)** - Development guidelines and build commands
+- **[UI Style Guide](src/UI/Windows/Styles/StyleGuide.md)** - Comprehensive design system and styling guidelines
+
+### Architecture Plans
+- **[Connection Plugin Architecture](docs/CONNECTION_PLUGIN_ARCHITECTURE.md)** - Plan for implementing pluggable connection types (Serial, Bluetooth, Network)
+
+### Localization
+- **[Localization Plan](docs/LOCALIZATION_PLAN.md)** - Multi-language support implementation
+- **[Language Switching](docs/LANGUAGE_SWITCHING_DEMO.md)** - Language switching functionality
+- **[Language Fixes](docs/LANGUAGE_SWITCHING_FIX.md)** - Language switching issue fixes
+
+## Contributing
+
+We welcome contributions! Please follow these guidelines:
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/amazing-feature`)
+3. Commit your changes (`git commit -m 'Add some amazing feature'`)
+4. Push to the branch (`git push origin feature/amazing-feature`)
+5. Open a Pull Request
+
+For documentation contributions:
+1. Place new documentation in the `docs/` directory
+2. Use descriptive filenames with `.md` extension
+3. Update this README to include the new file
+4. Follow the existing documentation style and structure
+
+## License
+
+This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENSE) file for details.
+
+## Contact
+
+Contact [Z-bit Systems, LLC](https://z-bitco.com) for inquiries regarding this project.
+
+## Related Projects
+
+- [OSDP.Net](https://github.com/bytedreamer/OSDP.Net) - The core OSDP communication library

ci/release.sh

@@ -0,0 +1,76 @@
+#!/bin/bash
+
+# OSDP-Bench Release Script
+# Merges develop into main to trigger CI version bump and release
+
+echo "OSDP-Bench Release Process"
+echo "=========================="
+echo ""
+
+# Ensure we have latest changes
+echo "Fetching latest changes..."
+git fetch --all
+
+# Check if there are uncommitted changes
+if [[ -n $(git status -s) ]]; then
+  echo "Error: You have uncommitted changes. Please commit or stash them before releasing."
+  exit 1
+fi
+
+# Ensure we're on develop branch
+CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
+if [[ "$CURRENT_BRANCH" != "develop" ]]; then
+  echo "Error: You must be on the develop branch to release. Currently on: $CURRENT_BRANCH"
+  exit 1
+fi
+
+# Pull latest develop
+echo "Updating develop branch..."
+git pull origin develop
+
+# Check if develop is ahead of main
+AHEAD_COUNT=$(git rev-list --count origin/main..origin/develop)
+if [[ "$AHEAD_COUNT" -eq 0 ]]; then
+  echo "Error: develop branch is not ahead of main. Nothing to release."
+  exit 1
+fi
+
+echo ""
+echo "Changes to be released:"
+git log --oneline --no-merges origin/main..origin/develop
+
+echo ""
+read -p "Do you want to proceed with the release? (y/n) " CONFIRM
+if [[ "$CONFIRM" != "y" ]]; then
+  echo "Release cancelled."
+  exit 0
+fi
+
+# Checkout main
+echo "Checking out main branch..."
+git checkout main
+
+# Pull latest main
+echo "Updating main branch..."
+git pull origin main
+
+# Merge develop
+echo "Merging develop into main..."
+git merge --no-ff develop -m "Release: Merge develop into main for automated release"
+
+# Push to remote
+echo "Pushing to remote..."
+git push origin main
+
+# Switch back to develop
+echo "Switching back to develop branch..."
+git checkout develop
+
+echo ""
+echo "Release process completed successfully!"
+echo "The CI pipeline will automatically:"
+echo "1. Run tests"
+echo "2. Bump version number"
+echo "3. Create a tagged release"
+echo ""
+echo "You can monitor the release progress in Azure DevOps."

crowdin.yml

@@ -0,0 +1,3 @@
+files:
+  - source: /src/Core/Resources/Resources.resx
+    translation: /src/Core/Resources/Resources.%two_letters_code%.resx

docs/ASYNC_INITIALIZATION_PATTERN.md

@@ -0,0 +1,71 @@
+# Async Initialization Pattern in ConnectViewModel
+
+## Problem
+The `ConnectViewModel` performs asynchronous initialization of serial ports in its constructor using `Task.Run`. This created testing challenges because:
+- Tests had to use unreliable `Task.Delay` to wait for initialization
+- No way to know when initialization completed
+- Race conditions could cause flaky tests
+
+## Solution
+We implemented a `TaskCompletionSource` pattern to track initialization completion:
+
+### 1. Added Initialization Tracking
+```csharp
+private readonly TaskCompletionSource<bool> _initializationComplete = new();
+
+/// <summary>
+/// Gets a task that completes when the initial serial port scan is finished.
+/// </summary>
+public Task InitializationComplete => _initializationComplete.Task;
+```
+
+### 2. Signal Completion in InitializeSerialPorts
+```csharp
+private async Task InitializeSerialPorts()
+{
+    try
+    {
+        // ... initialization logic ...
+        _initializationComplete.SetResult(true);
+    }
+    catch (Exception ex)
+    {
+        // ... error handling ...
+        _initializationComplete.SetException(ex);
+    }
+}
+```
+
+### 3. Use in Tests
+```csharp
+[Test]
+public async Task ConnectViewModel_InitializesSerialPortsOnStartup()
+{
+    // Arrange
+    var availablePorts = CreateTestSerialPorts();
+    SetupSerialPortMockWithPorts(availablePorts);
+
+    // Act
+    var newViewModel = new ConnectViewModel(...);
+
+    // Wait for initialization to complete
+    await newViewModel.InitializationComplete;
+
+    // Assert
+    Assert.That(newViewModel.AvailableSerialPorts.Count, Is.GreaterThan(0));
+}
+```
+
+## Benefits
+1. **Deterministic**: Tests wait exactly as long as needed
+2. **Reliable**: No race conditions or timing issues
+3. **Fast**: No unnecessary delays
+4. **Error handling**: Exceptions during initialization are properly propagated
+5. **Testable**: Different initialization scenarios can be tested (success, failure, no ports)
+
+## Alternative Patterns Considered
+1. **Factory pattern with async initialization**: Would require changing how ViewModels are created
+2. **Lazy initialization**: Would complicate the ViewModel usage
+3. **Synchronous initialization**: Would block the UI thread
+
+The `TaskCompletionSource` pattern provides the best balance of simplicity, testability, and maintaining the existing architecture.

CLAUDE.md → docs/CLAUDE.md

@@ -1,8 +1,11 @@
 # OSDP-Bench Development Guidelines
 
+## References
+- OSDP.Net source code: https://github.com/bytedreamer/OSDP.Net
+
 ## Build Commands
 - Build solution: `dotnet build OSDP-Bench.sln`
-- Build specific project: `dotnet build src/Core/Core.csproj`
+- Build a specific project: `dotnet build src/Core/Core.csproj`
 - Build release version: `dotnet build -c Release OSDP-Bench.sln`
 
 ## Test Commands
@@ -13,43 +16,24 @@
 
 ## Code Style Guidelines
 - Use C# 8.0+ features with async/await patterns for asynchronous operations
-- Follow MVVM design pattern for view models with ObservableObject and RelayCommand
+- Follow the MVVM design pattern for view models with ObservableObject and RelayCommand
 - Use dependency injection for services
 - Include XML documentation for public interfaces and methods
 - Use PascalCase for class, method, and public property names
-- Use _camelCase for private fields with underscore prefix
+- Use _camelCase for private fields with an underscore prefix
 - Implement defensive programming with null checks for constructor parameters
 - Use standard exception handling with try/catch blocks around external operations
 - Prefer async/await over direct Task management
 - Organize files into clear namespaces (Core, Models, Services, ViewModels, etc.)
 - Use meaningful variable names that reflect their purpose
 - Keep methods focused and small with a single responsibility
 
-## Refactoring Opportunities
-
-1. DeviceManagementService.cs: 
-   - Extract duplicate event raising patterns into helper methods
-   - Improve error handling in empty catch blocks
-   - Split long class (374 lines) into focused components
-
-2. ConnectViewModel.cs:
-   - Extract large switch statement in DiscoverDevice method
-   - Split ScanSerialPorts method with multiple responsibilities
-   - Simplify nested logic in ConnectDevice
-
-3. ManageViewModel.cs:
-   - Refactor 57-line ExecuteDeviceAction method
-   - Extract special handling for ResetCypressDeviceAction
-
-4. Consolidate nearly identical implementations:
-   - MonitorCardReads.cs and MonitorKeyPadReads.cs
-
-5. Test improvements:
-   - Remove duplicated setup code in ConnectViewModelTests.cs
-   - Increase test coverage beyond just ConnectViewModel
+## UI Style Guidelines
+- **Always use standard styles** - Apply predefined styles from the design system instead of inline properties
+- **Use design tokens for spacing** - Reference `{StaticResource Margin.Card}` instead of hardcoding values
+- **Apply semantic colors** - Use `{StaticResource Brush.Error}` instead of hardcoded colors like "Red"
+- **Follow the style hierarchy** - Check ComponentStyles.xaml and LayoutTemplates.xaml before creating custom styles
+- **Update existing code** - When modifying files, replace inline styling with standard styles
+- **Create reusable patterns** - If you find yourself repeating XAML structures, consider adding a new style or template
 
-6. Cross-cutting concerns:
-   - Standardize inconsistent error handling approaches
-   - Reduce ViewModels coupling to DeviceManagementService
-   - Fix naming inconsistencies (MonitorKeypadReads vs MonitorKeyPadReads)
-   - Convert hardcoded values (BaudRates, timeouts) to constants
+For detailed UI styling guidelines and examples, see: `src/UI/Windows/Styles/StyleGuide.md`