The following technology support list shows the .NET Framework that is arranged by features that are supported, not supported, limited support, limited and legacy support, and partially supported.

Supported

• 64-bit application development
• Application domains
• Assemblies
• Collections
• Common language runtime (CLR)

Not Supported

• .NET for Windows Store applications
• Accessibility
• Add-ins
• ASP.NET
• Assembly binding redirection
• Asynchronous programming
• Code DOM

Limited Support

• .NET Framework Class Library
• Common type system

Limited and Legacy Support

• Attributes

Partial Support

• ADO.NET

Supported

• Exceptions
• Generics
• Files and streams
• Interoperability
• Side-by-Side Execution in the .NET Framework

Not Supported

• Configuring Applications
• Data Service
• Debugging, tracing, and profiling
• Deploying applications
• Designers and the design environment
• Directory services
• Dynamic Language Runtime (DLR)
• GDI+
• Compressing files
• Image file handling
• Working with Images, Bitmaps, Icons, and Metafiles
• Images
• Lazy initialization
• Managed Extensibility Framework (MEF)
• Media and multimedia:
  • Graphics and Multimedia in Window Presentation Foundation
  • Graphics and Multimedia Portal
• Memory-mapped files
• Moving user interface elements
• MSBuild
• Network programming
• Out-of-band (NuGet) releases
• Parallel programming
• Portable Class Library
• Silverlight
• Transaction processing
• UI Automation
• WCF Data Services
• Windows Communication Foundation
• Windows Forms
• Windows Forms controls
• Windows Identity Foundation
• Windows Presentation Foundation (WPF)
• Windows services
• Windows Store applications
• Windows Workflow Foundation (WF)
• Zip files and archives

Limited Support

• Data access
• Globalization and localization
• I/O
• LINQ (Language-Integrated Query)
• Reflection
• Security in the .NET Framework
• Serialization
• Threading
• Windows Runtime
• XML documents and data

Partial Support

• Events

Implicit Only

• Garbage Collection

Classes in .NET are passed by reference, and cannot be used for integration as a result. Structures are passed by value, and the results can be passed between Java and .NET. Native types in the common type library are supported by default. Defined types must have a constructor if instance-based or declared as static if not.

Serialization of data between Java and .NET is possible, but direct serialization or synchronization of objects is not currently supported. The underlying APIs of Java and .NET do not support the level of object graph serialization required.

The Entity Framework uses a conceptual model to access an underlying data object. Because the model may have any type of design, some model types are not useful with the adapter. Some models are designed for update only, or access only by a data control object in a form. The ideal framework model for the adapter returns an object or contains an object query. Then object query can be serialized through a structure and array list for integration.