Watch, Follow, &
Connect with Us
Public Report
Report From: C#Builder    [ Add a report in this area ]  
Report #:  50463   Status: Reported
J# compiler support in C# Builder
Project:  C#Builder Build #:  NA
Version:    2005 Submitted By:   roland wu
Report Type:  Suggestion / Enhancement Request Date Reported:  8/13/2007 1:36:26 PM
Severity:    Commonly encountered problem Last Updated:
Platform:    All platforms Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (1 Total Rating)
4.00 out of 5
Total Votes: 3
I heard J# will be retired in Visual Studio 2008. Visual Studio 2005's product life cycle will be ended 2015. I don't know if CodeGear can support compiling J# or Java file from C# builder or in the future.

For supporting J# GUI building over .NET, it is not that important, because developers can always use C# or Delphi.Net to do it. However, for business logic, non-GUI libraries, such as SIP, H.323 protocol stack, ASN1 encoding library and communication framework, compilers and so on. All of them can be written in Java/J#. In this case, the user can just maintain one single source code in J# or Java.

C# and Java will coexist for a very very long time.  It seems Microsoft is not willing support J#/Java any more, so I feel this is an area maybe you can look at. I heard Delphi, C# builder themself also written in J#, so I guess you guys also have a need for J# compiler support in C# builder. I believe a lot of developers who are forced to use Java and .NET in the same project also have this need.

If you can have a good solution for this, I think C# builder might have chance to beat Visual C#.

Just a suggestion.

Steps to Reproduce:

roland wu at 8/20/2007 5:12:58 PM -
I did some research recently. Acutally ikvmc can compile Java byte code with debug info to MSIL. If I use VC# 2005, 2008 or DBGCLR.exe, it works pretty well.

I don't know if you guys should include IKVM project to C# builder.


Server Response from: ETNACODE01