2 little details on that page. For code-behind, it recommends to add "Base" to the code-behind file and use @inherit.
By doing so, whenever we use the component and type <MyComponent, it appears double, the base class and the actual class.
It should mention that you can have the code-behind with the same name (without Base), mark it as "partial", and you no longer need @inherit, and it connects the file correctly. This avoids having double-components in the list.
Also for Event Handlers, it could be good to mention that @on... syntax is only for built-in events, and that custom events do not use that syntax. Should custom events start with "On" by convention or not? The syntax is
<MyComponent Processing="Component_Processing" />
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 60c195c0-99f6-64f5-66a3-4e69109dc8ee
Version Independent ID: 24368808-4b90-f75a-e887-eb72a1c85f5b
2 little details on that page. For code-behind, it recommends to add "Base" to the code-behind file and use @inherit.
By doing so, whenever we use the component and type <MyComponent, it appears double, the base class and the actual class.
It should mention that you can have the code-behind with the same name (without Base), mark it as "partial", and you no longer need @inherit, and it connects the file correctly. This avoids having double-components in the list.
Also for Event Handlers, it could be good to mention that @on... syntax is only for built-in events, and that custom events do not use that syntax. Should custom events start with "On" by convention or not? The syntax is
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.