Forum › Xamarin.Forms
Quick Links
Why do I get these errors after upgrading to Xamarin Forms 4.0.0.425677 or above?
BillyMartin
USMember ✭✭✭
USMember ✭✭✭
No property, bindable property, or event found for 'Style', or mismatching type between value and property.
No property, bindable property, or event found for 'ItemsSource', or mismatching type between value and property.
in VS2019:
3.6.0.539721 works great, but the minute I upgrade, I get these errors.
in VS2017:
I get a bunch of Resource.designer.cs issues even with 3.6.0.539721
Tagged:
0
Best Answers
-
batmaci
DE ✭✭✭✭✭
this is not a valid declaration. Style="StaticResource transparentButtonStyle"
It wont even work on 3.6. i wonder how you could ever make that working in 3.65
Answers
Can you please share a simple sample about this problem? Any code about
StyleandItemsSource?Sure!
In App.xaml:
<Style x:Key="transparentButtonStyle" TargetType="Button"> <Setter Property="BackgroundColor" Value="Transparent" /> <Setter Property="TextColor" Value="White" /> <Setter Property="FontSize" Value="Large" /> <Setter Property="HorizontalOptions" Value="Start" /> </Style>In About.xaml:
<Button x:Name="WebsiteButton" Margin="0" BackgroundColor="Transparent" Clicked="GoToWebsiteAsync" FontSize="Large" Style="StaticResource transparentButtonStyle" Text="Visit Our Website" TextColor="Yellow" />this is not a valid declaration. Style="StaticResource transparentButtonStyle"
It wont even work on 3.6. i wonder how you could ever make that working in 3.6
When I commented them out, I started getting multiple errors about Colos.xml, Tabbar.xml, Style.xml, etc
What changed in Xamarin 4? Something to do with Material Theme, maybe?
The style should be:
Style="{StaticResource transparentButtonStyle}"Hmmm. It's been running fine in production for over a year, but I'll change it and let you know!
Wow! That did it. It's the little things, isn't it? LOL
Thanks so much!
your style wasnt applied probably in 3.6 but you didnt get also any error because xamarin didnt verify your xaml until 4.0. finally they enhanced XamlC to provide better build errors and you got the error, I assume.