What’s new for JLCA in Whidbey?


In a few days from now, come November 7th, the world of software development and developers would take a big leap ahead. Visual Studio a.k.a. Whidbey would be shipped. The product teams and the entire organization are very excited to have come so close to this milestone. And the excitement is increasing each day, as we come close to ship the product.


========
See excerpts from
Soma’s Blog below


… Recently at the Professional Developer’s Conference in Los Angeles, we made the first Release Candidate of Visual Studio 2005 available to attendees and MSDN subscribers …


… I want to encourage all of you to come out and see a launch event for yourself.  In addition to deep technical education and an opportunity to meet with the Microsoft employees who designed and built these products, you’ll be able to win valuable prizes and even free products.  To sign up for a launch event near you, please visit the launch portal site on Microsoft.com …
========


As we come closer to ship Visual Studio 2005, the users might find it helpful to know what’s new in JLCA in VS 2005.


JLCA 3.0 Whidbey is the next version of the tool. Featured to work with MS Visual Studio 2005 and .NET Framework 2.0, it has the ability to assist in the conversion of Java applications to .NET Framework 2.0.


Though there are not may feature additions for JLCA, the tool has become more robust. Numerous bug fixes have gone in for various product issues and to stabilize the previous release of the product. Some of the definitive advantages are
- JLCA now comes integrated with VS 2005: This would help us get out of the setup issues which some customers have faced in the previous add-on release of the product with VS .NET 2003
- Migrates J2EE applications to .NET Framework 2.0: Developers can now take advantage of the entire feature set provided in .NET Framework 2.0
- JLCA documentation is not separate but is integrated with MSDN for VS 2005


We would want to improve our product based on the customer needs. As we ship Whidbey and get started with the next release of the product we would love to hear back from you. Let us know as to what more you feel is needed in JLCA to help you migrate your code more efficiently. You may write to us at Java-Net@microsoft.com alias.

Comments (5)
  1. tim_vercruysse says:

    This may seem odd, but we have (as just part of our portfolio) an application with a LARGE body of Visual J++ code that currently runs on the Microsoft JVM. It leverages some proprietary Java extensions present in Microsoft J++. Will JCLA handle these extensions? If not, what’s the current advice from Microsoft on how to migrate J++ code onto .NET?

  2. freebsdlog says:

    what

  3. GauravS says:

    JLCA would assist migrating the VJ++ code to .NET Framework. You may want to take a look at the whitepaper located here – http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/dotnet_movingjavaapps.asp for the supported types.

  4. Hi,

    Can you help me in finding the JLCA feature in VS.NET 2005 IDE.

    ** URGENT **

    Thanks & regards

  5. GauravS says:

    Sharad, You may want to take a look at https://blogs.msdn.com/gauravseth/archive/2006/02/16/533425.aspx for more. This has the details.

Comments are closed.

Skip to main content