TonyG: New page will be enhanced over time

2009-01-17T10:10:29Z

New page will be enhanced over time

New page

<b>mv.NET</b> is a product which facilitates connectivity from .NET Framework code to almost all MV DBMS platforms.

Until time can be taken to provide a better summary here, have a look at the following resources:
*http://bluefinity.com/
*http://nebula-rnd.com/products/mvdotnet/
== Suppliers ==
The software is developed by <nowiki>BlueFinity International</nowiki>, a subsidiary of <nowiki>mPower1</nowiki>, which is also the parent company of <nowiki>jBase International</nowiki> and other companies. <nowiki>BlueFinity</nowiki> sells directly to VARs who bundle the software with their business software and to end-users. They also have a channel of regional and worldwide distributors who sell the software without application bundling to VARs and end-users, and provide support and development services.

== Uses ==
The software can be used to allow any external application or environment to connect into an MV application, and for MV DBMS applications to reach out to external environments. It is used extensively for thick-client, thin-client (ASP.NET), and Web Services interfaces. Also used for exchanges with relational DBMS environments.

== Benefits ==
*One product provides connectivity for almost all MV DBMS platforms, compared to vendor-specific libraries which are of no use to vendors who need to support multiple platforms.
*The Adapter Objects library allows .NET code to access the MV environment must like a relational environment without the developer needing to understand MV structures, and without an MV admin needing to flatten out the DBMS or create special dict items.
*One tool can be used to solve a multitude of "how do I" questions.
*Session pooling allows maximum efficient usage of MV DBMS licenses
*Integrated with Visual Studio including BASIC editor/compiler - all development can be performed from a single GUI IDE.

== Connectivity ==
The software uses the best methods available to connect into each MV DBMS:
*D3: Telnet or D3 Class Library
*jBASE: Telnet
*Universe and Unidata: Telnet or UO.NET
*Univision: Telnet or SAC
*QM: Telnet or <nowiki>QMClient</nowiki>
*mvBase, mvEnterprise, Power95, Advanced Pick, Reality: Telnet

== Competitors and Alternatives ==
*<nowiki>UniObjects</nowiki> and <nowiki>UniObjects.NET</nowiki>: These are actually used as the connectivity pipe under mv.NET into U2. mv.NET is a superset of these more basic libraries. UO and UO.NET are sometimes preferred because they are free and supported by IBM.
*PDP.NET / Pick Data Provider: Similar product from Raining Data (now <nowiki>TigerLogic</nowiki>) is no longer available.
*<nowiki>FusionWare</nowiki> products: Strong cost differences. <nowiki>FusionWare</nowiki> supports <nowiki>Unix/Linux</nowiki> clients, mv.NET does not.

Mv.NET - Revision history

TonyG: New page will be enhanced over time