---
title: "Discussion on \"Obfuscating strongly-typed configuration without breaking IOptions<T> binding\" | Hashnode"
description: "Discussion on \"Obfuscating strongly-typed configuration without breaking IOptions<T> binding\". A strongly-typed options class looks like the most ordinary C# in your solution — a POCO with public properties and nothing clever about it. But the moment you pass it to services.Configure<T>, a few"
url: "https://hashnode.com/posts/obfuscating-strongly-typed-configuration-without-breaking-ioptionst-binding/6af71c549e0edbe117b6efc0"
---

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

Discussion

# [Obfuscating strongly-typed configuration without breaking IOptions<T> binding](https://delta1labs.hashnode.dev/obfuscating-strongly-typed-configuration-without-breaking-ioptionst-binding?utm_source=hashnode&utm_medium=feed)

A strongly-typed options class looks like the most ordinary C# in your solution — a POCO with public properties and nothing clever about it. But the moment you pass it to services.Configure<T>, a few

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

-   [#obfuscation](https://hashnode.com/tag/obfuscation)
-   [#nebula](https://hashnode.com/tag/nebula)

## Written by

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

@clustron

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

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
