Why is Visual J# is not included in Visual Studio 2010 ?

Question

I heard that Visual J# is not included in Visual Studio 2008 and will not be included in future versions of Visual Studio . Is this true and why Microsoft made this kind of decision ?

Thank you ! 

Answer 1

Visual J# is dead. It has been discontinued by microsoft after VS2005. You can read more about the retirement of J# from microsoft website Retirement of J# language and Java Language Conversion Assistant from future versions of Visual Studio.


kaymaf

---

I hope this helps, if that is what you want, just mark it as answer so that we can move on

Answer 2

Why Microsoft made such kind of decision ? What are the reasons for J# failure ? I personally believe that J# had power of Java ( I mean Java Core Libraries ) and also rich .NET frame work.

Answer 3

it's mostly a marketing decision (after C# grew up and got momentum), but also cause they didn't want to invest money (now with the economical situation worldwide it's even worse) to add LINQ and other .NET3.x goodies to J# (not that they would be necessary though, since many people I feel want to use J# as a compatibility layer to have their Java code also running under .NET and integrating more easily with .NET apps - they want to use standard Java features, not the MS add-ons as with the old MSJava)

---

Microsoft MVP J# 2004-2009, Borland Spirit of Delphi 2001

Answer 4

I wish they would open-source it. As you say, all most of us are using it for is where we have java source that we need in .NET also.

---

Laugh your ____ off funny - Cubicle Wars

Answer 5

Can this group identify five MSFT Influentials who might help us to opensource VJ# into a codeplex project ?

---

Bob Palank

Answer 6

I could help if others are interested in too. Have been programming Java for more than a decade now (from around 1997) and .NET since 1.0.

Someone should first try to poll MS and Novell (the "mono" project guys) in case they want to take the initiative themselves using MS J# codebase and having Novell extend and support it for mono and for .NET.

If no interest I'd go for making a MonoJ# and highlighters etc. tools for Monodevelop IDE (and maybe also for Microsoft's VSX [Visual Studio Shell - standalone mode] and VisualStudio [integrated mode add-in]). I think if one goes with mono (and their version control system etc.) rather than .NET+Codeplex they may have more people behind the project

btw, should also checkout Grasshoper (commercial if I remember well, but may have some opensourced part) project and KVM.net

---

Microsoft MVP J# 2004-2009, Borland Spirit of Delphi 2001