Urgent.News

What's breaking now, across thousands of outlets.

Tech

How renaming breaks MVVM Toolkit bindings

A CommunityToolkit.Mvvm view-model is mostly code you never wrote. You declare a field and an attribute; a source generator produces the public property, the PropertyChanged plumbing and the command object at compile time. That is the appeal — and it is also why obfuscating such an app trips people up. The names XAML binds to are not in your source. They are generated, they are public, and some…

The MVVM Toolkit binding process relies on the names XAML binds to, which are generated and resolved by string at runtime. When renaming an assembly, the challenge is determining which generated names the runtime looks up by string and which were already wired as direct references. To avoid binding issues, it is crucial to keep the distinction in mind and apply the correct renaming strategy.

The generated IL code shows two types of names: strings and tokens. String names, such as FirstName and DisplayName, are used in property getters and setters, while token names, like FirstName in OnPropertyChanging(FirstName), are used for change notifications. Binding the runtime attempts to match the string name, and renaming the property will cause binding errors.

Commands, such as SaveCommand, are handled similarly, with the command property being resolved by string and other command-related names being kept. The recommended approach to renaming is to keep the public properties and commands on every view-model while renaming everything else in the assembly. This way, the binding layer continues to function correctly, and the rest of the code remains obfuscated and secure.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Arize Phoenix CVE-2026-53998: un fallo de cadena de formato con CVSS 10.0 filtra PHOENIX_SECRET sin iniciar sesión

Un fallo de cadena de formato en la consulta applyChatTemplate de Arize Phoenix (CVE-2026-53998, CVSS 10.0, del 16 de noviembre de 2026) permite a cualquiera que alcance una instalación por defecto…

  • Arize Phoenix vulnerability CVE-2026-53998 due to format string injection
  • Allows unauthorized access to PHOENIXSECRET without login
  • CVSS 10.0 rating classifies as critical threat

When one agent should become several specialists

Keep one agent on the whole task until the work breaks into specialties that need separate context and instructions. Mikiko Chandrasekhar put a practical size on that split: small agents equipped for…

  • Split a single agent into several specialized agents when it becomes too complex.
  • Log every handoff between agents for debugging and system inspection.
  • Measure quantifiable metrics like accuracy and runtime efficiency for coding agents.

Can a Vibe-Coded Healthcare App Be HIPAA-Compliant?

Vibe coding tools can generate a working healthcare application, but that doesn't mean the application is ready to handle protected health information (PHI).

  • Business Associate Agreements (BAAs) necessary when vendors handle PHI
  • Server-side authorization required to prevent unauthorized access to PHI
  • Patient-level auditability mandatory for tracking PHI access and modifications

More from Wednesday 18 November →