5.0.0 Migration Guide #3466
Replies: 6 comments 7 replies
-
|
Hello, how can i change the height of textbox outline ? |
Beta Was this translation helpful? Give feedback.
-
|
I assume you are looking to change the thickness of the outline? If so, the property you want to change is |
Beta Was this translation helpful? Give feedback.
-
|
Thank for your reply. |
Beta Was this translation helpful? Give feedback.
-
|
It sounds like you are likely already on the right path. The |
Beta Was this translation helpful? Give feedback.
-
|
Hi, regarding ShadowAssist.ShadowEdges, I'm getting an error that it doesn't exist, what name was it changed to? |
Beta Was this translation helpful? Give feedback.
-
|
It was functionally removed in #3217 and was removed in the 5.0.0 because it was no longer be respected by any of the controls. If it is still in use in your project, you can simply wrap the control and clip it to achieve the same visual effect. |
Beta Was this translation helpful? Give feedback.
-
|
hi, What is the best way to access these PrimaryXXX colors in version 5? |
Beta Was this translation helpful? Give feedback.
-
|
The brushes were renamed, but the colors are still available and can be referenced the same as before. However, be aware that all of the "Accent" resource dictionaries did have their names changed to be "Secondary" instead. Beyond that, all of the color resource dictionaries should be unchanged. You can see all of them here: https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit/tree/master/MaterialDesignColors.Wpf/Themes |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reply. I migrated to version 5 and in some parts of the code I used Static Resource PrimaryXXX colors that do not exist now. If I add What is the best way to access these PrimaryXXX colors in version 5? my App.xaml: |
Beta Was this translation helpful? Give feedback.
-
|
My apologies on the link we just recently redid the repo structure, which broke the link. Here is the updated one. As for accessing the colors, this works for me, and I am not seeing the issue with the theme problems you describe. App.xaml <Application.Resources>
<ResourceDictionary>
<ResourceDictionary.MergedDictionaries>
<materialDesign:BundledTheme BaseTheme="Inherit"
ColorAdjustment="{materialDesign:ColorAdjustment}"
PrimaryColor="DeepPurple"
SecondaryColor="Lime" />
<ResourceDictionary Source="pack://application:,,,/MaterialDesignColors;component/Themes/MaterialDesignColor.Amber.xaml" />
<ResourceDictionary Source="pack://application:,,,/MaterialDesignThemes.Wpf;component/Themes/MaterialDesign2.Defaults.xaml" />
</ResourceDictionary.MergedDictionaries>
...Then in my application: <Button Style="{StaticResource MaterialDesignFloatingActionMiniLightButton}"
ToolTip="MaterialDesignFloatingActionMiniLightButton">
<Button.Background>
<SolidColorBrush Color="{DynamicResource Primary400}" />
</Button.Background>
<materialDesign:PackIcon Width="{StaticResource IconSize}"
Height="{StaticResource IconSize}"
Kind="Alarm" />
</Button>In the demo app, this then looks something like this (first button is now using the Amber color). |
Beta Was this translation helpful? Give feedback.
-
|
Hi Keboo, i'm trying to override the defalut style but getting many error like this. |
Beta Was this translation helpful? Give feedback.
-
|
The issue here is that the BindableItemsHost is declared internal. What you want to do is download that file, change its namespace, and leverage that within your local copy of the template. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I'm updating from 4.9 to 5.1 and there's a converter called |
Beta Was this translation helpful? Give feedback.
-
This is a living document that is expected to be a guide for updating from 4.9.0 to 5.0.0. All feedback is welcome here, however if you are running into a specific issue with the migration, please open a new issue rather than commenting here.
This will cover the most common upgrade issues. You can find a list of breaking changes on issue: #2255.
Anything that was previously marked as Obsolete in the 4.9.0 or earlier release has been removed.
Main Defaults Resource Dictionary Renamed
Because we are still supporting both Material Design 2 and Material Design 3 styles, the previous
MaterialDesignTheme.Defaults.xamlresource dictionary has been replaced withMaterialDesign2.Defaults.xamlandMaterialDesign3.Defaults.xaml. In your main App.xaml replace with one of those two dictionaries. If you want your app to still use the same previous look and feel, theMaterialDesign2.Defaults.xamlresource dictionary most closely resembles the defaults from the 4.9.0 release.Brush Renames
To better facilitate the addition of new brushes as well as to make adjusting individual components, the library has adopted a new naming scheme for brush resources.
MaterialDesign.Brush.prefix.MaterialDesign.Brush.<Primary|Secondary>.[Light|Dark]. Corresponding foreground colors, will have a.Foregroundsuffix added. For exampleMaterialDesign.Brush.Secondary.LightorMaterialDesign.Brush.Primary.Foreground.For anyone wishing to avoid needing to do the brush rename at the time of upgrade, there is an additional resource dictionary that you can include that maps the old brush resource names to the new names. This would typically get placed in the merged resource dictionary of your App.xaml.
Be aware that this should be considered a temporary solution to allow time to do the full migration. It is not expected to be maintained long term and is subject to have items removed from it on future releases.
There is also a migration script that can be run on your repository that will attempt to locate brush resources and update them. Be aware this only looks for
{StaticResource xxx}and{DynamicResource xxx}references for brushes. You can find the script in the repository hereSee #2435 for more additional details.
Style renames
To standardize on naming, all usages of "Accent" in the style keys were replaced with "Secondary". For many style keys, simply making this one change will appropriately update it.
For anyone wishing to avoid needing to do the style rename at the time of upgrade, there is an additional resource dictionary that you can include that maps the old styles keys to the new names. This would typically get placed in the merged resource dictionary of your App.xaml.
Be aware that this should be considered a temporary solution to allow time for you to do the full migration. It is not expected to be maintained long term and is subject to have items removed from it on future releases.
There is also a migration script that can be run on your repository that will attempt to locate style resources and update them. Be aware this only looks for
{StaticResource xxx}and{DynamicResource xxx}style references. You can find the script in the repository hereShadowAssist replaced by ElevationAssist
The ShadowAssist was previously marked as Obsolete in the 4.9.0 release and has been completely removed int he 5.0.0 release.
To fix any usages simply update from
ShadowAssisttoElevationAssistandShadowDepthtoElevation. The old values map to the new ones as follows:ShadowDepth.Depth0=>Elevation.Dp0ShadowDepth.Depth1=>Elevation.Dp2ShadowDepth.Depth2=>Elevation.Dp3orElevation.Dp4ShadowDepth.Depth3=>Elevation.Dp7orElevation.Dp8ShadowDepth.Depth4=>Elevation.Dp12orElevation.Dp16ShadowDepth.Depth5=>Elevation.Dp16orElevation.Dp24Code renames
All extension method classes have had their "Mixin" suffix replaced with an "Extensions" suffix. In most cases, this will be a transparent change, unless you are invoking the extension method directly as a static method.
Beta Was this translation helpful? Give feedback.
All reactions