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.

Cloud Integration

Shield integrates with the ByteHide Cloud Panel to manage your protection lifecycle. From the panel you can create projects, view build history, track protection analytics, and decode obfuscated stack traces.

Your code never leaves your machine

Shield processes your application's binary locally on your build machine. Your source code, compiled binaries, and application resources are never uploaded or stored on ByteHide servers.

Getting Started with the Cloud Panel

1. Create a Project

Create your first project Click to expand

Create a Shield project Click to expand

2. Get Your Token

Once the project is created, copy your project token from the project dashboard and add it to your shield-ios.json configuration file. From this point on, every build automatically connects to the Cloud Panel.

Get your project token Click to expand

JSON

{
  "projectToken": "your-project-token",
  "protections": {
    "symbol_renaming": true,
    "string_encryption": true,
    "anti_debug": true
  }
}

{
  "projectToken": "your-project-token",
  "protections": {
    "symbol_renaming": true,
    "string_encryption": true,
    "anti_debug": true
  }
}

3. Configure Protections

You can manage your protection configuration from the shield-ios.json file, or review and compare configurations across builds from the Cloud Panel.

Protection configuration Click to expand

Build History

Every build with Shield is recorded in the Cloud Panel. The build history shows timestamps, protection configurations, analytics, and provides access to mapping files and stack trace deobfuscation for each build.

Shield build history Click to expand

From the build history you can compare protection configurations between builds, download mapping files for any past build, and decode obfuscated stack traces directly from the panel.

Protection Analytics

The Cloud Panel tracks protection metrics across all your builds, including symbols processed, strings encrypted, methods renamed, build execution time, and protection quota usage.

Protection analytics Click to expand

Project Token - Obtaining and configuring your token
Deobfuscate Stack Traces - Decoding obfuscated crash reports
CI/CD Integration - Configuring Shield in CI pipelines