- Additional Q&A about breaking changes can be found here
- To ask a question about breaking changes use this
| 7488094 | [ErrorTracker] content.valid writing to a read only observable Previously the valid observable was not typed correctly so you would not get a compiler error when trying to write to it (instead it would show up at runtime as an MDS error). Now we're typing valid as read only so the compiler will flag issues in extension code. This does not change behavior at all since previously any writes to the valid() observable on controls were discarded and did nothing. |
| 6725007 | Launch notice blade when resource type does not support move operation No description available for this breaking change. |
| 6655921 | ExtensionDefinition is now a required class Extensions are expected to define a class that derives from Microsoft.Portal.Framework.ExtensionDefinition. And export it with the following MEF attribute: [Export(typeof(ExtensionDefinition))] internal class MyExtensionDefinition : ExtensionDefinition This has always been required and extensions who do not define this correctly tend to have unexpected behavior. This change now enforces this and the extension will fail at app startup if such a class is not found. This is to avoid the unexpected behavior at runtime. |
| 6632356 | Remove old hubs related code Removes support for specifying hubs in PDL since hubs have been deprecated. |
| 5637012 | Resource move type validation This change removes the supportsResourceMove option for the ResourceSummary view-model. Resources will be opted in automatically when the RP indicates the resource type supports moving resources between resource groups and/or subscriptions. Simply remove the option to resolve the build break. Contact ibizafxpm@microsoft.com if you need to opt out of resource move when your RP supports it. |