Framework support · Technical announcement
Skater .NET Obfuscator now supports .NET 11 assemblies
Protect the implementation you ship—not just the source code you keep.
By Rustemsoft LLC · Product compatibility announcement
Redeveloped for .NET 11. Tested beyond a single sample.
Rustemsoft has redeveloped Skater .NET Obfuscator to support protection of assemblies built for .NET 11. The updated tool has been tested extensively with several types of .NET 11 applications. This is support for the new assembly target—not simply a change to a framework label on the website.
The protection capabilities below are established Skater features applied to the new target. This announcement does not claim that every protection technique is new in .NET 11, or that every deployment model and third-party dependency has been certified.
Before and after: readable names become implementation noise
The Skater manual demonstrates renaming with a “Hello World! Today is:” application. These shortened IL excerpts reproduce the documented member-name changes.
Before protection
.class private auto ansi sealed beforefieldinit Module1
.field private static string str
.field private static valuetype [mscorlib]System.DateTime today
.method public static void Main() cil managed
IL_0000: ldstr "Hello World! Today is:"After alphanumeric renaming
.class private auto ansi sealed beforefieldinit '0AAAA'
.field private static string '1AAA0'
.field private static valuetype [mscorlib]System.DateTime '2AAAA'
.method public static void '1AAAA'() cil managed
IL_0000: ldstr "Hello World! Today is:"Module1 becomes '0AAAA'; str becomes '1AAA0'; today becomes '2AAAA'; Main becomes '1AAAA'. The string literal remains readable because this particular example demonstrates renaming, not string encryption.
This is an abbreviated legacy example from the Skater manual, not output captured from a .NET 11 test. Its [mscorlib] references are retained from the original. The separate excerpts omit method bodies and are not complete IL programs.
Match .NET 11 release requirements to Skater features
Moving to a new target framework does not remove existing compatibility requirements. Choose protection around the contracts your application must preserve.
| Release requirement | Skater capability | Application consideration |
|---|---|---|
| Protect managed .NET 11 output | Assembly-level processing | Load the managed assembly built for the new target; validate the transformed artifact. |
| Reduce readable implementation clues | Member renaming | Preserve names required by public contracts or name-based access. |
| Conceal useful string literals | Selective string encryption | Review runtime dependencies and deployment requirements. |
| Complicate analysis of critical logic | Control flow obfuscation | Apply incrementally and measure runtime behavior. |
| Protect WPF resources and code | XAML/BAML protection | Test bindings, resources, and application navigation. |
| Repeat protection in release builds | Saved profiles, XML settings, and CLI | Check edition availability; archive settings with the release. |
Threats and protection techniques for .NET 11 assemblies
These are managed-code risks relevant to .NET 11 applications, not vulnerabilities introduced specifically by .NET 11. Layer techniques according to the implementation details you need to protect.
| Inspection or abuse risk | Protection technique | Practical limit |
|---|---|---|
| Readable type and method names | Member renaming | Removes semantic clues; does not make program behavior unknowable. |
| Static searching for messages and licensing clues | String encryption | Raises inspection effort; strings still need runtime access. |
| Easy reconstruction of method logic | Control flow transformation | Complicates analysis; test output size, stability, and performance. |
| Inspection of WPF UI implementation | XAML/BAML protection plus assembly protection | Resource protection does not replace testing bindings and name-dependent code. |
| Tracing sensitive license decisions | Layered renaming, strings, control flow, and optional licensing | Licensing features depend on edition and configuration; no absolute anti-piracy guarantee. |
The manual documents renaming, string encryption, control flow, WPF protection, and licensing. Obfuscation raises the cost of analysis; it is not a guarantee that determined attackers cannot inspect or modify client-side software.
Configure protection in Skater
The manual illustrates the interfaces used to inspect assemblies and select protections. Documentation screenshots are interface references, not evidence of a particular .NET 11 test run.
Info tab
Inspect assembly properties and the assembly structure. View the illustrated manual.
Control Flow tab
Select methods and a control-flow algorithm. View the illustrated manual.
Strings tab
Select string values and storage options. View the illustrated manual.
Licenser
Configure the documented application-licensing workflow. View the illustrated manual.
A practical .NET 11 protection workflow
- Build and test your unprotected application first. Keep a baseline artifact for comparison.
- Open the managed assembly in Skater and inspect it on the Info tab. Preserve public members required by external callers.
- Configure renaming, selected string protection, and control flow according to your application. Start conservatively with name-dependent and performance-sensitive code.
- Save the settings. For automation, use a named profile or an XML configuration file with the documented command-line interface.
- Obfuscate, then re-sign strong-named assemblies with the appropriate key where required. Package any generated string DLLs or other required runtime dependencies.
- Run release tests against the protected output. Archive the tool version, settings, and renaming map alongside your release records.
Use the documented XML-profile command
Skater -x=C:/MyDir/MyAssemblySettings.xmlThis is the manual’s example syntax; replace the path with your saved XML profile. The CLI should not run while the GUI is open. Command-line availability depends on edition: consult the current comparison.
Validate the application you actually distribute
Rustemsoft’s extensive .NET 11 testing establishes the basis for this support announcement; it does not replace testing your own protected application.
- Exercise reflection, dynamic invocation, serialization, and externally consumed public APIs.
- For WPF, verify bindings, resource loading, and navigation.
- Check native interop and deployment of any generated dependency files.
- Compare startup, memory use, and performance-sensitive paths with the baseline build.
- Verify exception handling and logging, and retain the renaming map for support diagnostics.
The manual’s control-flow testing guidance covers reflection, serialization, interop, and performance. Do not infer universal support for Native AOT, trimming, single-file publishing, every runtime identifier, or every third-party library from this announcement; validate the exact deployment configuration you use.
Frequently asked questions
Does Skater .NET Obfuscator support .NET 11?
Yes. Rustemsoft has redeveloped Skater to support protection of assemblies built for .NET 11 and has extensively tested it with several types of .NET 11 applications. Validate your own protected release before distributing it.
Why do some Skater pages still mention .NET 10 or an earlier version?
Documentation and other website pages are being updated after this announcement. Older framework references do not reflect the newly announced .NET 11 support.
What does Skater change in an assembly?
Depending on the selected settings, Skater renames members, encrypts selected string literals, and transforms method control flow. WPF applications can also use its documented XAML/BAML protection.
Can I rename every public member?
Not safely in every application. The manual advises preserving public members used by external assemblies. Review name-dependent behavior and test reflection, serialization, and dynamically invoked code.
Can obfuscation run from a build script?
Yes. The documented command-line interface accepts saved GUI profiles and XML configuration files. Check the edition comparison for command-line availability and keep the GUI closed while running the CLI.
Does string encryption make embedded secrets unrecoverable?
No. The manual explains that strings are decrypted at runtime and that a determined attacker may recover them. String protection makes static inspection harder; it is not a substitute for keeping sensitive secrets outside a distributed client.
What should I test before shipping a protected .NET 11 application?
Run functional and integration tests against the protected output, including reflection, serialization, native interop, startup, and performance. Preserve required public names, include generated dependencies, re-sign strong-named assemblies where required, and retain the renaming map for diagnostics.
Documentation and related guides
Protect your next .NET 11 release
Use Skater’s updated .NET 11 support with a protection profile tailored to your application. Start with the download, review edition availability, and validate the final protected build.