lor=blue>Help for Webmasters « back to results for ""
Below is a cache of http://www.mainsoft.com/solutions/pdfs/IBuySpy.pdf. It's a snapshot of the page taken as our search engine crawled the Web.
The web site itself may have changed. You can check the current page or check for previous versions at the Internet Archive. Yahoo! is not affiliated with the authors of this page or responsible for its content.
Porting ASP.NET Applications to the J2EE




Porting ASP.NET Applications to
the J2EE Platform



A case study that demonstrates the ease of porting the
Commerce Starter Kit application to J2EE






January 2005
www.mainsoft.com


Porting .NET Applications to the
J2EE Platform
A case study that demonstrates the ease of porting the
Commerce Starter Kit application to J2EE


INTRODUCTION ........................................................................................................................................ 3

VISUAL MAINWIN OVERVIEW............................................................................................................. 4

B
UILDING A
V
ISUAL
M
AIN
W
IN
J2EE

A
PPLICATION
................................................................................... 4

D
EBUGGING A
V
ISUAL
M
AIN
W
IN
J2EE

A
PPLICATION
................................................................................ 5

R
UNTIME
L
IBRARIES
................................................................................................................................... 5

PORTING .NET APPLICATIONS TO J2EE ........................................................................................... 5

PORTING THE ASP.NET COMMERCE STARTER KIT TO J2EE.................................................... 5

W
HAT IS THE
C
OMMERCE
S
TARTER
K
IT
A
PPLICATION
?.............................................................................. 5

P
ORTING
P
ROCESS
....................................................................................................................................... 6

Step 1: Configure the porting machine................................................................................................... 6

Step 2: Set up the Commerce Starter Kit................................................................................................ 7

Step 3: Run the Commerce Starter Kit application................................................................................. 7

Step 4: Port the Commerce Starter Kit application to J2EE ................................................................... 9

P
RODUCTIVITY
B
ENCHMARKS
................................................................................................................... 15

P
ERFORMANCE
.......................................................................................................................................... 15

PORTING CHALLENGES....................................................................................................................... 15

T
HIRD
-P
ARTY
L
IBRARIES
.......................................................................................................................... 16

C
ODE
M
ODIFICATIONS
.............................................................................................................................. 16

SUCCESS THROUGH PARTNERSHIP................................................................................................. 17

F
IXED
-C
OST
,

F
IXED
-T
IME
A
PPROACH FOR
P
ORTING
................................................................................. 17

T
HE
M
AINSOFT
P
ORTING
M
ETHODOLOGY
................................................................................................ 18

Step 1: Requirement Analysis .............................................................................................................. 18

Step 2: Detailed Project Plan ................................................................................................................ 18

Step 3: Implementation......................................................................................................................... 18

Step 4: On-Site Project Delivery .......................................................................................................... 19

C
ONCLUSION
............................................................................................................................................. 19

ABOUT MAINSOFT ................................................................................................................................. 19


Introduction
Many developers favor the Visual Studio .NET
®
development
environment to write their applications because it is easy to use
and highly productive. However, due to changing business
requirements, companies often choose to deploy business-critical
applications on the J2EE platform.
The challenge facing Independent Software Vendors (ISVs) and IT
organizations is to capitalize on the productivity of .NET without
sacrificing the scalability and flexibility of J2EE servers. Until now,
conflicting software standards have required these companies to
invest in overlapping resources and skills, driving up their
development and maintenance costs.
Many ISVs and IT organizations would welcome a cost-effective
solution to deploy their .NET Web applications and Web services on
J2EE, without having to rewrite their entire applications in Java.
ISVs want to offer their products on both .NET and J2EE, without
making significant investments in resources and skills. Enterprises
face a similar challenge when they opt to deploy existing .NET
enterprise applications and Web services on J2EE servers.
Mainsoft developed Visual MainWin
®
for the J2EE platform to
resolve the development and deployment challenges arising from
the .NET/J2EE divide. Visual MainWin enables Visual Studio
developers to port .NET Web applications and Web services to the
J2EE platform from Visual Studio, dramatically reducing time-to-
market and development costs. With the Commerce Starter Kit case
study, we demonstrate the ease of porting .NET applications written
in C# or Visual Basic.NET
®
to the J2EE platform.
For the past decade, Mainsoft has helped many of the worlds
largest ISVs, such as Computer Associates, IBM Rationale, and
Siebel Systems, to deploy enterprise-class applications on non-
Microsoft
®
platforms on time and on budget, slashing development
costs and time-to-market by as much as 75 percent.
Visual MainWin Overview
Visual MainWin is a complete development solution that includes:
A development environment that is fully integrated into Visual
Studio .NET. Visual MainWin inherits all the productivity
features that make Visual Studio such a popular development
tool and can be used by .NET developers to develop, deploy, and
debug J2EE applications, without additional training.
A patent-pending compiler that compiles Microsoft Intermediate
Language (MSIL) into standard Java bytecode.
A set of .NET runtime extensions to J2EE servers that enable
.NET applications to run on any standard J2EE application
server, such as IBM WebSphere
®
, BEA WebLogic
®
, JBoss
®
, or
Tomcat.
Building a Visual MainWin J2EE Application
Developers can write programs in either C# or Visual Basic.NET
and compile their source code directly into standard Java bytecode.
Mainsoft's binary compiler is integrated seamlessly into the build
process. When the user builds a project, Visual MainWin
automatically compiles the MSIL assemblies and generates Java
bytecode. The Java class files are then packed in standard JAR or
WAR files and deployed transparently on the J2EE application
server.

Figure 1 - Binary compilation from MS Intermediate Language to Java bytecode
Visual MainWin provides new types of C# and Visual Basic.NET
projects, including templates for an ASP.NET Web Application, an
ASP.NET Web Service, a Web Control Library, a Class Library, and
a Console Application. When building any one of these projects, a
J2EE application is created. Debugging a Visual MainWin J2EE Application
Visual MainWins patent-pending debugger enables C# and Visual
Basic.NET developers to debug applications running on a Java
Virtual Machine (JVM) within Visual Studio .NET, without seeing
the actual runtime Java symbols. The debugger connects to the
JVM where the application is running and sends debugging
commands such as breakpoints, steps, and continues. Data
received from the debugger is translated back into the original
source language and displayed in the Visual Studio debugger user
interface.
Runtime Libraries
Visual MainWin provides a Java implementation of the ASP.NET
and ADO.NET class libraries. This implementation of .NET class
libraries is based on the
Mono
project, a high-quality o