From: Wjhonson > You stated below that its transportable. > Maybe you could give a few examples of what mv.NET can do for > those who don't need the transportable feature.
Fair question. I'll provide some examples here but invite anyone with more detailed interest to contact me directly. - mv.NET includes a code generator which creates strongly typed classes from U2 files. You can pass an assembly to someone who has never seen the MVDBMS and they'll see a collection of Customers, with individual Customer objects that only expose what you want them to see. One developer might just get name/address info, another will get read-access to accounting data, and another will get read/write access to contact info. Of course you can create POCO's manually but you don't need to. The generated classes can use your BASIC programs for read/write/select. And because they're partial classes you can intercept/insert/override functionality. - mv.NET includes sophisticated session management to ensure you have processes to respond to inbound requests, and you can manage exactly how that's done for all of your applications in one easy to use interface. - mv.NET includes built-in paging for selections. Most new multi-tier developers will code a Select and populate a list box with the results, and Then realize that this doesn't work well when a million records are in the pipe. But here your code can set a retrieval interval and just pull data in batches, as needed. - mv.NET includes an RPC class which allows the DBMS to trigger client-side events. - It has a built-in XAML generator/editor for Silverlight. - It has built-in web services for those who don't want to roll their own. - Similar to UO.NET it also has a built-in ADO.NET class library, allowing developers more familiar with relational databases to operate on U2 data in a manner that's more convenient for them. Note, this doesn't mean you need to do SQL queries against your MV DBMS - it means it looks relational to them without you needing to do anything on your side. For every one of those and other features, different people will say "I can do that on my own". In my experience about 50% of the people who say that about many features might be able to. But the point is that even those folks will wind up writing a lot of wrapper code that's already built into this other product. And they'll need to maintain it. How much is your time worth? Is "free" software really free when you spend That much time building on features? The decision here is up to the individual. After writing my own connectivity products for years I decided to stop doing the lower-end stuff so that I could focus on higher-end apps and interfaces. YMMV. HTH Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com Nebula R&D sells mv.NET worldwide and provides related development services http://Nebula-RnD.com/blog http://Twitter.com/TonyGravagno _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
