Feature: Migrate profile files from xml to json

[BornToBeRoot]

Changes proposed in this pull request

• Migrate profile files from xml to json

Copilot generated summary

Provide a Copilot generated summary of the changes in this pull request.

Copilot summary

This pull request introduces a major migration for profile storage in ProfileManager.cs, moving from XML-based profiles to a new JSON-based format. It adds support for detecting, migrating, and backing up legacy XML profiles, ensures consistent JSON serialization, and updates all relevant serialization logic. The changes also introduce events and logging to track the migration process, and provide backup mechanisms for legacy files.

Profile format migration and serialization updates:

• Changed the default profile file extension from .xml to .json, added a legacy XML extension for migration, and implemented consistent JSON serialization options using System.Text.Json.
• Updated all serialization and deserialization methods to use JSON by default, including writing and reading profiles, and provided methods to handle both JSON and legacy XML formats for backward compatibility. [1] [2] [3] [4]

Legacy XML profile migration and backup:

• Implemented detection and migration logic for legacy XML profile files (including encrypted files): on loading, the code now detects XML content, migrates it to JSON, creates backups, and removes the old files after migration. [1] [2] [3] [4]
• Added a backup folder and methods to store backups of legacy XML files before migration, and updated file discovery to include both JSON and legacy XML profiles. [1] [2]

Migration process events and logging:

• Added events (OnProfileMigrationStarted, OnProfileMigrationCompleted) and corresponding methods to signal the start and completion of profile migration, along with detailed logging throughout the migration process for better traceability. [1] [2] [3]

These changes ensure a smooth transition from XML to JSON profile storage, improve maintainability, and provide robust handling and auditing of the migration process.

To-Do

• Update changelog to reflect this changes

Contributing

By submitting this pull request, I confirm the following:

• I have read and understood the contributing guidelines and the code of conduct.
• I have have added my name, username or email to the contributors list or don't want to.
• The code or resource is compatible with the GNU General Public License v3.0.

[Copilot]

Pull request overview

This pull request implements a significant migration of the profile storage system from XML to JSON format. The changes include comprehensive migration logic with automatic backup creation, support for both encrypted and unencrypted profiles, and temporary events to signal migration progress.

Key Changes

• Profile file format changed from XML to JSON with automatic one-time migration on first load
• Migration creates timestamped backups in a dedicated Backups subfolder before converting files
• Added migration events (OnProfileMigrationStarted and OnProfileMigrationCompleted) marked as obsolete for future removal

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 17 comments.

File	Description
Website/docs/changelog/next-release.md	Documents the XML to JSON migration, automatic conversion behavior, and backup strategy
Source/NETworkManager/MainWindow.xaml.cs	Registers migration event handlers and removes unused import statement
Source/NETworkManager.Settings/SettingsManager.cs	Renames parameter from settingsFilePath to filePath for consistency with profile backups
Source/NETworkManager.Profiles/ProfileManager.cs	Core migration implementation including JSON serialization, XML detection, legacy file handling, and backup functionality

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.