Hello Domingo,

Thank you for the detail. The issue is under investigation. I would back to you as soon as we got the result from our developer.

Regards,
Handy

Hello Domingo,

Can you help us in providing the sample that simulates this issue? We need this to understand your issue issue deeply.

Regards,
Handy

Hi Olof,

You can try the dynamic binding by using Register View Identifier. For further information, you can refer into this link under Registering a View Identifier at Runtime section. Hope this helps.

Regards,
Handy

Instead of setting DrawerViewModel or TabbedViewModel as the root view model, you can use your own view model as the login page, for example, LoginViewModel and set it as the root view model in the AppService in the Core PCL project. Then create a new page for each platform that consumes the LoginViewModel, where you can implement your own custom logic and validation for the login process. We are currently creating a business template that streamlines this process for our customers and will be available in the next version of Crosslight.

We suggest to use a dedicated ViewController instead of using a modal dialog for the login form, as this will allow you to manage the login process easily in the view model. However, if you wish to use a modal dialog instead, you can create your own custom presenter and show the presenter right after the Navigated event in the view model. You can see our video in the YouTube channel that shows you how you can introduce your own custom presenters to use in Crosslight.

Hello,

Can you re-attach or re-upload the sample with another links? The current one was corrupted.

however, is there any guide wherein we can start projects from scratch? Are there any technical documentations for the setup class files like Infrastructure\AppService.cs? Or what is IApplicationInitializer? When can we use InitializeApplication, InitializeComponent, InitializeServices? Does it support dependency injection via constructors? Things like that...

Actually, We expect user only need to use our extension without need much configuration or do from the scratch. The wizard is only the tools to help user easily do the development. But if you want to do from the scratch, you can try to see more explanation in here.

Using crosslight is targetted for multiple platform (I get that), but we can't always focus on platform-specific (views) at the same time even with 90% shareable code. So we might skip other projects. Do you have plans on creating crosslight project templates individually?

Thank you for the feedback. Actually, you can uncheck which platform that you want to create with our wizard.

In addition, does crosslight support viewcontrolles created via code? If so, how do we create views and child controls in order for crosslight to bind the view and viewmodel properly? Here's a sample project in an attempt to start from small beginnings. The binding in this project don't work, so kindly review if you can.

Surely,it does support. In InitializeView, you can call this.RegisterViewIdentifier("AddButton", addButton);
Which "AddButton" is the outlet of the view and "addButton" as the button view itself. This should be registerred in the Binding Provider. For more information, you can refer into this link, under 'Registering a View Identifier at Runtime'.

Regards,
Handy