mv.NET

• The Core Objects library allows a .NET developer to write code using object-oriented syntax which is familiar to Pick programmers. The library allows for opening accounts and files, reading item/records, manipulating dynamic arrays, and using a familiar query language on files to select and sort data. By itself this is a complete and capable library, and the one most commonly used for front-end development.
• The Binding Objects library allows MV data to be used as the DataSource for data-bound components such as textboxes, lists, and grids. An object is created consisting of a list of items and other data. This object is then assigned as a component data source. There is no need to manually loop to read and insert the data into these complex components. As well as providing data to the user interface, data bound to components can update the database – often with little or no manual coding. Binding Objects can be used with both thick client Windows Forms, and to create Ajax-enabled ASP.NET browser interfaces.
• The Adapter Objects make the MV environment fully accessible as a true ADO.NET data source. The core of ADO.NET is the dataset, which contains tables and schema information. Many products have standardized to accept data in the form of a dataset - it is through this common denominator that they communicate with disparate data sources. While the dataset itself is organized like a small relational database, the actual database which ADO.NET reads from and writes to can be anything, including a non-relational MV DBMS. The Adapter Objects library of mv.NET allows MV data to be described in a manner which allows smooth import and export through a dataset. In other words, mv.NET functions as an ADO.NET Data Provider, which can be used with common products like Crystal Reports, Microsoft Excel, and a wealth of other products.

mv.NET is integrated with Visual Studio 2005 for the .NET Framework 2.0. (Older VS2003/.NET 1.1 is available, .NET 3 is in development) In addition to making use of mv.NET with C#, VB.NET and other languages directly from the VS2005 IDE, developers can access the MV DBMS to edit BASIC code using a built-in code editor with colored-syntax. The Visual Studio environment can also be used to maintain file data and standard and extended dictionary definitions.

mv.NET is built upon a robust communications framework. .NET Remoting is used for communications from a client or web server to a Session Manager process. This handles all open connections to one or more MV databases. A middle-tier License Manager controls access from any client to any server. “Best-method” tools are used to access each different MV platform. For example, telnet is used as the communications protocol into D3 and jBASE, UO.NET is used as a simple pipe to access Universe and Unidata, and QMClient is used to access QM. With mv.NET managing its own platform-independent communications, business applications are much more easily written on one MV platform and then deployed on another.

Licenses are available for application Development and for end-user Runtime sessions. mv.NET includes a session pooling manager to maximize effective use of existing DBMS licenses.

Nebula Research and Development sells and supports mv.NET and provides development services and other services for integrating mv.NET into existing environments.

© 2007 Nebula Research and Development