How to integrate ByteHide Shield with .NET projects?

Install the ByteHide.Shield.Integration NuGet package, configure your project token, and build your project. Protection applies automatically during MSBuild compilation.

Which .NET frameworks are supported by Shield?

Shield supports .NET Framework 4.0+, .NET Core 2.0+, .NET 5-8+, .NET Standard, Xamarin, MAUI, Unity, Blazor, ASP.NET, WPF, and WinRT.

How to configure Shield protection settings?

Configure Shield through MSBuild properties, environment variables, or the bytehide.json configuration file. Set protection levels, exclusions, and runtime options.

How to troubleshoot Shield integration issues?

Enable verbose logging, check build output for error messages, verify project token configuration, and ensure compatible .NET version and MSBuild tools.

How to exclude specific assemblies from protection?

Use the ExcludeAssemblies MSBuild property or add exclusion rules in bytehide.json configuration file to skip protection for specific assemblies or namespaces.

How to verify Shield protection was applied?

Check MSBuild output for Shield processing messages, examine protected assembly metadata, or use reflection tools to verify obfuscation was applied.

How to configure Shield for Unity projects?

Install Shield Unity package, configure project token in Unity settings, enable IL2CPP backend, and ensure compatible Unity version (2019.4+).

How to set up Shield in CI/CD pipelines?

Set project token as environment variable, ensure NuGet package restore, configure MSBuild parameters, and handle licensing for build agents.

Swift Metadata Stripping

Protection ID: swift_stripping

Swift Metadata Stripping removes Swift type information, debug symbols, and metadata from your application binary. This eliminates a rich source of information that reverse engineers use to understand your application's type hierarchy and structure.

Configuration

JSON

{
  "protections": {
    "swift_stripping": true
  }
}

{
  "protections": {
    "swift_stripping": true
  }
}

How It Works

Swift applications contain extensive type metadata in the binary. This metadata includes type names, protocol conformances, generic type parameters, reflection information, and debug symbols. Tools like swift-demangle can decode this metadata to reconstruct the full type hierarchy of your application.

Swift Metadata Stripping removes this information from the binary. After protection, demangling tools cannot recover meaningful type names, and reflection-based analysis is significantly limited.

This complements Symbol Renaming by removing the Swift-specific metadata that would otherwise survive name obfuscation.

What Gets Stripped

Metadata Type	Description
Swift symbols	Mangled Swift symbol names
Debug info	DWARF debug information
Type metadata	Swift type descriptors and conformance records

When to Use

Swift Metadata Stripping is recommended for all Swift applications. Swift binaries contain significantly more metadata than Objective-C binaries, and this metadata provides a detailed map of your application's architecture. Stripping it is a low-cost, high-value protection that complements other obfuscation measures.

Symbol Renaming - Rename identifiers
Class Encryption - Encrypt Objective-C metadata
Protections Overview - All available protections

Configuration

How It Works

What Gets Stripped

When to Use

Related