This section provides a list of features that are supported and not supported.

Note: This is not a complete list and anything not on this list is implied to be not supported. For more information, contact your customer support representative.

.NET Application Essentials

The following is a list of areas that are not supported:

• Widows Store, Widows Forms, XAML, any display methods
• Dynamic assemblies
• Network I/O
• SOAP Serialization
• Write to console

Using .NET serialization classes are not supported for integration.

.NET Data and Modeling

Area not supported (WCF)

Not supported for integration (Writing to a file or XML file)

The following restrictions apply for the Entity Framework (.NET areas):

• Windows Presentation Foundation and Windows forms (not supported)
• Common Client technologies (not supported)
• Windows Service applications (not supported)
• Parallel and asynchronous processing (not supported)
• Windows Communication Foundation (not supported)
• Windows Identity Foundation (not supported)
• Windows Workflow Foundation (not supported)
• Platforms other than Windows client or server (not supported)

The following is a technology support list for the .NET Framework:

.NET Framework 4.5 and 4 scope list:

• 64-bit application development (supported)
• .NET for Windows Store applications (not supported)
• .NET Framework Class Library (limited support)
• Accessibility (not supported)
• Add-ins (not supported)
• ADO.NET (partial support)
• Application domains (supported)
• ASP.NET (not supported)
• Assemblies (supported)
• Assembly binding redirection (not supported)
• Asynchronous programming (not supported)
• Attributes (limited and legacy support)
• Code DOM (not supported)
• Collections (supported)
• Common language runtime (CLR) (supported)
• Common type system (limited support)

Configuration:

• Configuring Applications (not supported)
• Data access Limited Support
• Data Service (not supported)
• Debugging, tracing, and profiling (not supported)
• Deploying applications (not supported)
• Designers and the design environment (not supported)
• Directory services (not supported)
• Dynamic Language Runtime (DLR) (not supported)
• Events (partial support)
• Exceptions (supported)
• Garbage Collection (implicit only)
• GDI+ (not supported)
• Generics (supported)
• Globalization and localization (limited support)
• I/O (limited support)
• Files and streams (supported)
• Compressing files (not supported)
• Image file handling (not supported)
• Working with Images, Bitmaps, Icons, and Metafiles (not supported)
• Images (not supported)
• Interoperability (supported)
• LINQ (Language-Integrated Query) (limited support)
• Lazy initialization (not supported)
• Managed Extensibility Framework (MEF) (not supported)
• Media and multimedia:
  • Graphics and Multimedia in Window Presentation Foundation (not supported)
  • Graphics and Multimedia Portal (not supported)
• Memory-mapped files (not supported)
• Moving user interface elements (not supported)
• MSBuild (not supported)
• Network programming (not supported)
• Out-of-band (NuGet) releases (not supported)
• Parallel programming (not supported)
• Portable Class Library (not supported)
• Reflection (limited support)
• Security in the .NET Framework (limited support)
• Serialization (limited support)
• Side-by-Side Execution in the .NET Framework (supported)
• Silverlight (not supported)
• Threading (limited support)
• Transaction processing (not supported)
• UI Automation (not supported)
• WCF Data Services (not supported)
• Windows Communication Foundation (not supported)
• Windows Forms (not supported)
• Windows Forms controls (not supported)
• Windows Identity Foundation (not supported)
• Windows Presentation Foundation (WPF) (not supported)
• Windows Runtime (limited support)
• Windows services (not supported)
• Windows Store applications (not supported)
• Windows Workflow Foundation (WF) (not supported)
• XML documents and data (limited support)
• Zip files and archives (not supported)

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.

Common Language Runtime Scope

The adapter uses the .NET unmanaged COM API to instantiate the .NET Common Language Runtime (CLR). The .NET CLR is not an emulated environment, but communication with the instance is governed by the adapter. There are several languages that can generate CLI code. The adapter has been extensively tested with C# and on a more limited basis with source from Visual Basic and F#. For adapter usage requirements with any other language, contact your customer support representative.

No explicit or implicit guarantee of compatibility or performance with user application components is given with the iWay .NET Technology Adapter. The scope of the framework is too wide and deep to do so. If you have specific questions about supported components of .NET or application compatibility, contact your contact your customer support representative.