---
title: "Discussion on \"Obfuscating a WinForms app without losing your designer resources\" | Hashnode"
description: "Discussion on \"Obfuscating a WinForms app without losing your designer resources\". If you have obfuscated a WPF app you already know the one rule there: XAML binds to view-model members by name, so those names have to survive. WinForms looks similar — a desktop app, a .Designer.cs f"
url: "https://hashnode.com/posts/obfuscating-a-winforms-app-without-losing-your-designer-resources/6af3288c4d349388ef339d72"
---

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

Discussion

# [Obfuscating a WinForms app without losing your designer resources](https://delta1labs.hashnode.dev/obfuscating-a-winforms-app-without-losing-your-designer-resources?utm_source=hashnode&utm_medium=feed)

If you have obfuscated a WPF app you already know the one rule there: XAML binds to view-model members by name, so those names have to survive. WinForms looks similar — a desktop app, a .Designer.cs f

1d ago · 7 min read · delta1labs.hashnode.dev  
Read the article

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

## Written by

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

@clustron

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

## Responses

Markdown supported · ⌘↵ to post

No responses yet.