Handles clause event handler execution order limits

Event Handler Invocation Sequence

In Visual Basic .NET, the Handles clause provides a declarative way to subscribe methods to events of WithEvents variables. This mechanism removes the need for explicit AddHandler calls during object initialization.

A specific design challenge arises when multiple methods within the same class are declared to handle the same event. While the runtime typically invokes these handlers based on their sequence in the source code, the language specification does not formally guarantee a deterministic execution order.

This creates uncertainty for implementations that require a specific sequence of side effects across different handler methods for a single event trigger.

• Does the VB.NET compiler guarantee the execution order of multiple Handles methods across different versions?
• What is the recommended architectural pattern to ensure a strict sequence of operations when multiple methods must respond to the same event?