Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
It would be super helpful to be able to determine if the ContentPage/ContentView is being rendered at runtime or for the Previewer.
Use cases for this would be:
- When animations manipulate your views/controls but you want to see the after-animation in the Previewer. Example here: https://github.com/xamarin/Sport/blob/master/Sport.Mobile.Shared/Pages/WelcomeAuthentication/EnablePushPage.xaml.cs#L23
- If you are setting your BindingContext in C#, you may want to set a mock VM instead of the runtime VM.
- Properties getters don't play nice in Preview mode but work fine at runtime
Ideally, something like the Windows Forms .IsDesignMode property.... like FormsApplication.Current.IsPreviewMode
I've added this to the team backlog.
There is also a proposal from John Miller in Evolution, though we need to decide on the actual naming and implementation.
I would hope we replicate one of the existing mechanisms exposed by WPF/UWP. Converging the feature set seems like the right approach!