Review: Code In .Net, Run On J2EE

Solving interoperability with third-party bridging technologies can alleviate some of the complexities. But since most of these enterprise-bus products use proprietary solutions to optimize communication, applications become intricately dependent on them. Integrators must be aware that by not locking low-level access to specific technologies, they are essentially shifting to old models often used by EAI vendors. Adhering to standards should take precedence whenever possible, so enterprise applications aren't bound to proprietary solutions.

Visual MainWin solves all of those issues because it provides an open-ended architectural solution. It doesn't tie architects to any vendor solution. Porting code also can solve all interoperability problems, but that's extremely expensive for development. Web services offer a simpler alternative, but Test Center engineers believe that Visual MainWin can make it cost-effective.

Visual MainWin covers C#, ASP.Net, VB.Net and most of the .Net framework. WinForms for building Windows forms, though, can't be converted because there are no direct alternatives on other platforms such as Linux. When using third-party components, developers must recompile them into Java so that .Net applications can use them on the Java side.

If source code from third-party software isn't available, customers have to buy a Java implementation of that software or abstract the services provided by the software through code. The correct way to work with many third-party applications is to abstract services from those products. If that practice isn't put in place, porting code then becomes extremely difficult and Mainsoft's solution won't work.

The new Visual MainWin 1.8 Portal Edition promotes what it calls .Net extensions to work with the IBM WebSphere portal software. These extensions are ASP.Net code running natively inside the WebSphere portal. The Visual MainWin enterprise version works with WebSphere, JBoss and BEA WebLogic and includes multi-CPU capabilities. It also can consume EJBs. Visual MainWin, too, is now able to work with Remoting and .Net System.DirectoryServices on J2EE.

Visual MainWin costs $5,000 per developer seat and $2,500 per CPU. Mainsoft provides in-person technical training and offers on-site technical support, including phone support. The company offers an average margin of 30 percent, and solution providers also can earn revenue by providing complete support when porting .Net applications. Mainsoft funds 50 percent of joint marketing and lead generation for up to $5,000 per year.