Skip to main content
BuyLog In
XAF: Cross-Platform .NET App UI & Web API
Search in…
Docs > Debugging, Testing and Error Handling > Automatic Code Error Diagnostics > XAF0017: Incompatible assemblies must not be added to the same project
All docs
V25.1
    • .NET Framework 4.6.2+
    XAF: Cross-Platform .NET App UI & Web API
    .NET Support and Migration
    Getting Started
    Installation, Upgrade, Version History
    Backend Web API Service
    UI Shell and Base Infrastructure
    Storage, ORM, and Business Model Design
    Data Manipulation and Business Logic
    User Interface and Behavior Customization
    Data Filtering
    Application Security and Data Safety
    Multi-Tenancy (Data per Tenant)
    Validation (Prevent Data Errors)
    Conditional Appearance (Manage State of UI Elements)
    Reporting (Shape, Export & Print Data)
    Analytics (Extract Data Insights)
    Document Management
    Business Process Management
    Event Planning
    Localization
    Accessibility Support
    Debugging, Testing and Error Handling
    Debug, Collect and Analyze the Diagnostic Information
    Log Files
    Automatic Code Error Diagnostics
    XAF0001: Implement XPO business class constructors correctly
    XAF0002: XPO business class properties should not be overridden
    XAF0003: XPO business classes should be public
    XAF0004: Implement XAF controller constructors correctly
    XAF0005: XAF controller classes should be public
    XAF0006: Invalid target platform. Change the target platform to "Any CPU" in the project or solution properties
    XAF0007: The Build Action property of the XAFML file must be set to Embedded resource
    XAF0008: The current Visual Studio version is not supported or .NET 9+ SDK is not installed
    XAF0009: Properties decorated with the RuleRequiredFieldAttribute should be of nullable or reference type
    XAF0010: Set the DelayedAttribute.UpdateModifiedOnly property to True
    XAF0011: Implement the delayed property correctly
    XAF0012: Avoid calling the XafApplication.CreateObjectSpace() method overload without the Type parameter
    XAF0013: Avoid reading the XafApplication.ConnectionString property
    XAF0014: The property with the Association attribute must have a correct unique pair
    XAF0015: Association must not have the Aggregated attribute if it is paired to the "many" end of the association
    XAF0016: Descendants of NonPersistentBaseObject and NonPersistentLiteObject must be decorated with the DomainComponent attribute
    XAF0017: Incompatible assemblies must not be added to the same project
    XAF0018: Avoid creating a new Session/UnitOfWork with parameterless constructors in XPO-based projects
    XAF0019: Apply ExplicitLoadingAttribute only to reference properties
    XAF0020: Avoid applying NonPersistentAttribute to properties without a public setter
    XAF0021: Create new controllers correctly
    XAF0022: Avoid using the ShowViewStrategy.ShowView method
    XAF0023: Do not implement IObjectSpaceLink in the XPO classes
    XAF0024: Do not implement IXafEntityObject in the XPO classes
    XAF0025: Use the corresponding XAF ORM-agnostic or Entity Framework attribute
    XAF0026: Use the supported version of EF Core packages
    XAF0027: Do not apply DomainComponentAttribute to the XPO business class
    XAF0028: Use the corresponding XPO attribute
    XAF0029: Use the enclosing property name in a method call
    XAF0030: Use generic members without the type parameter to declare your association property
    XAF0031: Add the UseChangeTrackingProxies() call for automatic UI updates
    XAF0032: Use the explicit syntax to create an instance of the CriteriaOperator class
    XAF0033: EF Core business class properties should not be overridden
    Unit Tests
    End-to-End (Functional) Tests
    Performance Optimization
    Error Handling in ASP.NET Core Blazor and Web Forms
    Hot Reload Support (ASP.NET Core Blazor)
    Deployment
    Support, QA & Troubleshooting
    API Reference
    Download CHM

    XAF0017: Incompatible assemblies must not be added to the same project

    Severity: Warning

    Assemblies from different platform-specific applications (WinApplication, WebApplication, BlazorApplication) must not be referenced in the same project. For example, do not reference the DevExpress.ExpressApp.Dashboards.Blazor.v22.1.dll and DevExpress.ExpressApp.Dashboards.Win.v22.1.dll assemblies in the same project.

    How to Fix

    Reference only those packages that are actually used in your project. Remove platform-specific assembly references from the MySolution\Module project.