You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
You'll see results like below with several error messages (21 below) that include "Can not". Some of these errors are pretty common, like the "Can not find the object referenced by {Name}" error I encountered earlier today.
It should be "Cannot" (one word). That's preferred usage, even though the two word version is technically acceptable in English. See https://www.dailywritingtips.com/cannot-or-can-not/
If you grep the Xamarin.Forms source for "Cannot" you'll see it's also used most often.
./Xamarin.Forms.Controls.Issues/Xamarin.Forms.Controls.Issues.Shared/Issue7773.cs: [Issue(IssueTracker.Github, 7773, "[Android] Can not set Entry cursor position by tapping if ClearButtonVisibility=WhenEditing", PlatformAffected.Android)]
./Xamarin.Forms.Core/BindableObject.cs: Log.Warning("BindableObject", $"Can not set the BindableProperty \"{property.PropertyName}\" because it is readonly.");
./Xamarin.Forms.Core/BindableObject.cs: Log.Warning("SetValue", $"Can not convert {value} to type '{property.ReturnType}'");
./Xamarin.Forms.Core/ImageSource.cs: Internals.Log.Warning("Warning", "Can not find CallingAssembly, pass resolvingType to FromResource to ensure proper resolution");
./Xamarin.Forms.Core/Interactivity/BindingCondition.cs: throw new InvalidOperationException("Can not change Binding once the Condition has been applied.");
./Xamarin.Forms.Core/Interactivity/BindingCondition.cs: throw new InvalidOperationException("Can not change Value once the Condition has been applied.");
./Xamarin.Forms.Core/Interactivity/DataTrigger.cs: throw new InvalidOperationException("Can not change Binding once the Trigger has been applied.");
./Xamarin.Forms.Core/Interactivity/DataTrigger.cs: throw new InvalidOperationException("Can not change Value once the Trigger has been applied.");
./Xamarin.Forms.Core/Interactivity/EventTrigger.cs: Log.Warning("EventTrigger", "Can not attach EventTrigger to {0}.{1}. Check if the handler exists and if the signature is right.", bindable.GetType(), Event);
./Xamarin.Forms.Core/Interactivity/PropertyCondition.cs: throw new InvalidOperationException("Can not change Property once the Trigger has been applied.");
./Xamarin.Forms.Core/Interactivity/PropertyCondition.cs: throw new InvalidOperationException("Can not change Value once the Trigger has been applied.");
./Xamarin.Forms.Core/Interactivity/Trigger.cs: throw new InvalidOperationException("Can not change Property once the Trigger has been applied.");
./Xamarin.Forms.Core/Interactivity/Trigger.cs: throw new InvalidOperationException("Can not change Value once the Trigger has been applied.");
./Xamarin.Forms.Core/Layout.cs: throw new InvalidOperationException("Can not add self to own child collection.");
./Xamarin.Forms.Core/NavigationModel.cs: throw new InvalidNavigationException("Can not pop final item in stack");
./Xamarin.Forms.Core/NavigationModel.cs: throw new InvalidNavigationException("Can not pop final item in stack");
./Xamarin.Forms.Platform.iOS/Renderers/SwipeViewRenderer.cs: Log.Warning("SwipeView", "Can not load SwipeItem Icon.");
./Xamarin.Forms.Platform.UAP/NativeEventWrapper.cs: Log.Warning(nameof(NativeEventWrapper), "Can not attach NativeEventWrapper.");
./Xamarin.Forms.Xaml/ApplyPropertiesVisitor.cs: xpe = xpe ?? new XamlParseException($"Can not set the content of {((IElementNode)parentNode).XmlType.Name} as it doesn't have a ContentPropertyAttribute", node);
./Xamarin.Forms.Xaml/MarkupExtensions/ReferenceExtension.cs: throw new XamlParseException($"Can not find the object referenced by `{Name}`", serviceProvider);
The text was updated successfully, but these errors were encountered:
Description
Grep the Xamarin.Forms source for "Can not".
You'll see results like below with several error messages (21 below) that include "Can not". Some of these errors are pretty common, like the "Can not find the object referenced by
{Name}
" error I encountered earlier today.It should be "Cannot" (one word). That's preferred usage, even though the two word version is technically acceptable in English. See https://www.dailywritingtips.com/cannot-or-can-not/
If you grep the Xamarin.Forms source for "Cannot" you'll see it's also used most often.
The text was updated successfully, but these errors were encountered: