/

Framework-Specific Guidance

Framework-Specific Guidance

ByteHide Shield is designed to work with all .NET frameworks and platforms. This section provides tailored guidance for specific frameworks to help you get the most effective protection while maintaining full compatibility.

Supported Frameworks

<div id="avalonia"></div>

Avalonia

Official Partnership: ByteHide Shield is an official partner of Avalonia UI, providing seamlessly integrated protection for Avalonia applications.

  • Out-of-the-box support: No special configuration needed - Shield automatically detects and optimizes for Avalonia
  • XAML preservation: Special handling for Avalonia XAML resources and UI components
  • Cross-platform compatibility: Maintains all functionality across Windows, macOS, and Linux

Learn more about Avalonia protection

Unity

Unity applications have specific requirements due to their compilation model and runtime environment:

  • IL2CPP considerations: Tailored protections for IL2CPP compilation process
  • Asset protection: Strategies for securing Unity assets alongside code
  • Performance optimizations: Balancing security with runtime performance

Learn more about Unity protection

Blazor

Protecting Blazor applications requires special considerations:

  • WebAssembly considerations: Special handling for WASM-compiled Blazor applications
  • Server-side protection: Strategies for securing server-side Blazor components
  • Client-side security: Techniques for securing client-visible code

Learn more about Blazor protection

MAUI / Xamarin

Mobile and cross-platform applications built with MAUI or Xamarin:

  • Platform-specific considerations: Tailored protection for iOS, Android, and other platforms
  • Resource protection: Securing embedded resources on mobile platforms
  • Performance impact: Minimizing protection overhead for mobile devices

Learn more about MAUI/Xamarin protection

AOT Compilation

Applications using Ahead-of-Time compilation:

  • Native AOT support: Special considerations for .NET Native and other AOT compilation models
  • Performance impact: Understanding how protections work with pre-compiled code

Learn more about AOT protection

Framework-Specific Configuration

While Shield automatically adapts to most frameworks, you can use configuration files to fine-tune protection settings for specific frameworks:

{
  "framework_specific": {
    "avalonia": {
      "enabled": true
    },
    "unity": {
      "enabled": true,
      "il2cpp_compatibility": true
    }
  }
}

Learn more about configuration options to fine-tune framework-specific behavior.

Next
Introduction