IBM and Mainsoft Ink Deal To Integrate .NET Apps -- Visual Studio Magazine

IBM and Mainsoft Ink Deal To Integrate .NET Apps

By Kurt Mackie
11/21/2007

It just got a little easier for developers using Microsoft's .NET Framework technology and SharePoint to integrate their .NET applications with IBM's Java-based portal technology. In a global reseller deal, IBM agreed to sell Mainsoft Corp.'s .NET Extensions solution with the IBM WebSphere Portal solution.

IBM WebSphere Portal lets users create composite or "mashup" applications. It's designed for service-oriented architectures and enables organizational performance monitoring, self-service applications, document access and team collaboration.

Organizations may have various reasons to migrate to IBM WebSphere Portal, but tighter interoperability among portals may be a key objective.

"Portal-to-portal interoperability is going to become increasingly important," said Yaacov Cohen, Mainsoft's CEO and president. "With a service-oriented architecture you want to connect all of your systems together, and you want to deliver your composite applications -- coming from different platforms."

Mainsoft's technology, according to a Mainsoft press release, can integrate a number of Microsoft .NET technologies:

Windows SharePoint services;
Microsoft Office document libraries;
SQL Server Reports; and
.NET-based applications.

Mainsoft, an advanced IBM business partner, provides solutions that help organizations with mixed .NET and Java environments. The company's solutions are certified as "Optimized for Visual Studio" and have been validated as "Ready for WebSphere Software."

The .NET Extensions suite encompasses the functionality of two of Mainsoft's products: Mainsoft Portal Edition and Mainsoft SharePoint/SQL Reporting Federator.

Mainsoft Portal Edition solution is a plug-in to the Visual Studio development environment. It has a cross-compiler that compiles .NET code into Java bite code. The solution makes it easier for developers with a background in C# and Visual Basic to integrate ASP.NET on WebSphere Portal.

Mainsoft SharePoint/SQL Reporting Federator is an add-on to Mainsoft Portal Edition. It helps federate data in SharePoint and Microsoft's SQL Reporting Services within WebSphere Portal. The add-on product currently works with WebSphere Portal Server versions 5.1 and 6.0.

.NET developers don't need to know Java to use Mainsoft's solution to compile Java bite code.

"From a developer's perspective, you don't need to learn Java," Cohen said, "but in order to achieve a high level of integration on the portal server, you typically need to learn about portal concepts."

Mainsoft offers a three-day class to help developers get up to speed.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.