Hi Fabian,

To add a server-side query, you will need to extend the controller by adding the desired method that will be called from the client. While in the client, you can use named query which is built into the DataListViewModel.

To learn more how it works, please download the sample here. Pay attention to the CategoryListViewModel.cs in the Core project, and the InventoryController.Partial.cs in the web project.

Hope this helps.

Hello Max,

Yes, it is possible to use the table structure you mentioned with Crosslight's user management. In fact, Crosslight's service is designed to be very flexible and as data agnostic as possible, so you can use any kind of table structure in your apps. You just have to carefully remap the entities/properties in existing functions to your own entities/properties.

Since you're also using ASP.NET Identity (although newer version), it should be easier to adjust the current template to the referred table. Note that Crosslight's user management extends and customizes the original IdentityContext, so you should be able to map the required properties in OnModelCreating method of the particular entity context as well.

On the other hand, we will also include an agenda in our roadmap for ASP.NET Identity 2.0 support.

Hope this helps.

Hello Fabian,

Yes, it is possible to navigate to different target (ViewModel) in the list. In the binding provider of the list, bind the table view to the DetailNavigationTargetProperty and specify the property that will be queried during navigation.

Finally, in the list ViewModel, you added a property that corresponds to the binding definition. You can then put the logic in the property's getter and return the desired NavigationTarget. This flexibility allows you to navigate to any kind of different page based on your condition, not just limited to two.

The example of the property definition would look like the following:

public NavigationTarget Target{
    get
    {
        if (someCondition)
             return new NavigationTarget(typeof(ViewModelA));
        else
             return new NavigationTarget(typeof(ViewModelB));
    }
}

Hope this helps.

Hello Thomas,

Thanks for your issue report. It seems the Xamarin 8.4 introduces several breaking changes which will investigate and resolve soon.

However, we noticed that you are still using Xamarin iOS Classic project. We highly recommend you to upgradeyour project to Xamarin iOS Unified, which should work fine with the latest build (172). Furthermore, projects without 64 bit support will no longer approved by Apple by Feb 1st.

Hope this helps.

Hi Ryan,

Thanks for reporting this issue. The missing templates was due to the new project type introduced for XamarinUnified iOS. However, if your iOS project is still classic, the Crosslight iOS templates should appear properly.

We plan to ship the new iOS templates for Unified project type in this month's update.

Hope this helps.