Babel Obfuscator full changelog

Enhancements:
Added support for .NET 9.0 SDK: Ensures compatibility with the latest .NET framework, allowing developers to seamlessly integrate with .NET 9.0.
Introduced a Blazor app agent task: Simplifies and optimizes the obfuscation process for Blazor-based applications.
Enhanced Babel CLI: Streamlines workflows by enabling direct CLI handling of complex projects with multiple targets without using MSBuild.exe
Improved XAML obfuscation for MAUI applications: Enhances the security and compatibility of XAML elements within MAUI projects.
Changes:
Removed support for .NET 5.0 SDK in Babel Obfuscator NuGet package.
Bug Fixes:
Resolved a startup crash affecting Blazor assemblies.
Fixed an issue where the XAML Style property attribute could not be properly resolved.
Corrected dead code removal for structs tagged with InlineArrayAttribute.
Addressed a crash in ILCompiler caused by an incorrect embedded portable PDB format, resulting in the error: “Specified argument was out of the range of valid values. (Parameter ‘length’).”
Updated Babel UI: In the “Edit Rules” panel, assembly-scoped rules now display correctly in the root namespace.
Cross assembly renaming for custom attributes accepting enums in constructor arguments.

Enhancements:
Added support for .NET 9 preview: Stay updated with the latest .NET framework by utilizing obfuscation support for .NET 9 preview.
Implemented code encryption for .NET Standard 2.1 components: Enhanced security features now allow code encryption within .NET Standard 2.1 projects.
Babel UI: Enabled editing of licensee-related fields: Users can now directly edit licensee fields in the Babel UI for easier license management.
Babel UI: Improved performance to avoid locking the UI when displaying licenses and customer tables with many records: The UI now handles large datasets more efficiently, ensuring a smoother experience without freezes or delays.
Babel CLI: Introduced a new command-line switch –warningsasinfos, allowing users to treat warning messages as informational messages. This feature offers greater flexibility for users who prefer to reduce the prominence of warnings during the obfuscation process, making logs cleaner and focusing attention on more critical issues.
Bug Fixes:
Resolved issue where satellite assemblies were not processed for “zh” culture-related folders: Ensured correct handling of satellite assemblies for Chinese culture-specific folders.
Corrected behavior to avoid renaming XAML labels if they contain symbol names: Improved the XAML processing logic to prevent unwanted renaming of labels.
Fixed license file validation error when the file is locked by another process: Handled locked files gracefully during license validation.
Fixed dynamic proxy issue when the return type has required or optional modifiers: Ensured proper dynamic proxy handling when dealing with return types with modifiers.
Resolved a Babel crash caused by a NullReferenceException in scenarios where the target assembly is only partially read: Enhanced stability by fixing crashes due to partially read assemblies.
Resolved an issue where Babel could not resolve BAML dotted properties: Improved handling of BAML dotted property resolution.
XAML Setter Value pro

This update brings bug fixes, and increased stability.
Bug Fixes:
Fix: babel.exe could crash with object reference not set exception on cross assembly renaming.
Fix: babel.exe could consume a large amount of memory leaks processing XML map files.

Enhancements:
[New] PDB Support for NuGet Symbol Packages: We have added support for Program Database (PDB) files in NuGet symbol packages (.snupkg). With this enhancement, Babel Obfuscator now seamlessly integrates with NuGet symbol packages that contain PDB files.
Bug Fixes:
Fix: Resolved an issue where Babel Obfuscator would crash with the error message “An error occurred during phase ‘Memory Writer’: COM object that has been separated from its underlying RCW cannot be used.” This bug has been addressed, ensuring a more stable and reliable obfuscation process.

Bug Fixes:
The JSON dependency manifest is not updated when embedding .NET Core assemblies.
XML license validation could raise the error: XML document not loaded.
Fix: PInvoke adds .dll extension to non windows library imports