---
title: "Discussion on \"Obfuscating a WinUI 3 app: what {x:Bind} already made rename-safe, and the three strings that still break it\" | Hashnode"
description: "Discussion on \"Obfuscating a WinUI 3 app: what {x:Bind} already made rename-safe, and the three strings that still break it\". A WPF obfuscation guide does not transfer to WinUI 3, and a UWP one only half-transfers, because the thing that decides what survives a rename is the XAML compiler, and WinUI 3's is closer to Avalonia"
url: "https://hashnode.com/posts/obfuscating-a-winui-3-app-what-xbind-already-made-rename-safe-and-the-three-strings-that-still-break/6af57b158f470ae4c63447bd"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Obfuscating a WinUI 3 app: what {x:Bind} already made rename-safe, and the three strings that still break it](https://delta1labs.hashnode.dev/obfuscating-a-winui-3-app-what-xbind-already-made-rename-safe-and-the-three-strings-that-still-break?utm_source=hashnode&utm_medium=feed)

A WPF obfuscation guide does not transfer to WinUI 3, and a UWP one only half-transfers, because the thing that decides what survives a rename is the XAML compiler, and WinUI 3's is closer to Avalonia

2d ago · 10 min read · delta1labs.hashnode.dev  
Updated 2h ago  
Read the article

-   [#nebulanet](https://hashnode.com/tag/nebulanet)
-   [#obfuscation](https://hashnode.com/tag/obfuscation)
-   [#dotnet](https://hashnode.com/tag/dotnet)
-   [#deepdive](https://hashnode.com/tag/deepdive)

## Written by

[Zero Heartbeat](https://hashnode.com/@clustron)

@clustron

  
[View profile](https://hashnode.com/@clustron)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.