Can you provide examples of successful projects using both MvvmCross and CSLA.net

Overview of MvvmCross

MvvmCross is a cross-platform MVVM framework designed for Xamarin applications. It facilitates the creation of loosely coupled, maintainable, and testable mobile solutions by providing a robust MVVM architecture. MvvmCross applications typically consist of a core project containing view models, models, and business logic, and native projects for each platform (e.g., Android, iOS) that handle the user interface and platform-specific services[1][4].

Overview of CSLA.net

CSLA.net is a business object framework that supports multiple platforms, including Windows, Android, and iOS. It provides a robust set of features for managing business objects, including data binding, validation, and business rules. CSLA.net can be used with various MVVM frameworks to manage the business logic layer of an application[2][10].

Integration of MvvmCross and CSLA.net

To integrate MvvmCross with CSLA.net, you would typically use CSLA.net for the business object layer and MvvmCross for the application and UI level support. Here’s how you might structure such a project:

1. Business Logic Layer (CSLA.net):**
- Use CSLA.net to define your business objects. These objects would encapsulate data and business rules.
- CSLA.net provides features like validation and data binding that can be leveraged in your view models.

2. ViewModel Layer (MvvmCross):**
- Create view models that inherit from CSLA.net's `ViewModelBase` class. This allows you to leverage CSLA.net's features while still adhering to the MVVM pattern.
- Use MvvmCross's dependency injection and IoC container to manage services and interfaces needed by your view models.

3. UI Layer (Platform-specific):**
- Implement platform-specific UI components using native controls for Android and iOS.
- Use MvvmCross's binding engine to connect your view models to the UI components.

Example Structure

Here's a simplified example of how you might structure a view model that uses both MvvmCross and CSLA.net:

csharp
using MvvmCross.Core.ViewModels;
using Csla;

public class MyViewModel : ViewModelBase
{
    private readonly IMyService _myService;

    public MyViewModel(IMyService myService)
    {
        _myService = myService;
    }

    // Example property bound to the UI
    public string Name
    {
        get { return MyBusinessObject.Name; }
        set { MyBusinessObject.Name = value; RaisePropertyChanged(() => Name); }
    }

    // Example command
    public IMvxCommand SaveCommand => new MvxCommand(Save);

    private void Save()
    {
        // Use CSLA.net's business object to perform validation and save
        MyBusinessObject.Save();
    }
}

In this example, `MyBusinessObject` is a CSLA.net business object, and `MyViewModel` is an MvvmCross view model that leverages CSLA.net's features.

Challenges and Considerations

- Portable Class Libraries (PCLs): CSLA.net business objects may not be compatible with PCLs due to their complexity, so you might need to use file linking instead of PCLs for these classes[2].
- Validation and Business Rules: Ensure that CSLA.net's validation and business rules are properly integrated with your MvvmCross view models to maintain a clean separation of concerns.

While there are no specific documented projects combining MvvmCross and CSLA.net, the theoretical integration outlined above provides a solid foundation for building robust, cross-platform applications that leverage the strengths of both frameworks.