In the SDK installed docs, under “Using LAPI in a .NET Environment” it says this:
Before you begin LAPI development in Microsoft Visual Studio .NET, you must
install the Microsoft Visual J# .NET Redistributable Package 1.1, which can be
downloaded from the Microsoft Web site at:
http://msdn.microsoft.com/vjsharp/downloads/howtoget.asp
That website doesn’t exist, but the vjsharp (http://msdn.microsoft.com/vjsharp) one does, although there a lots of Javascript errors in it – and under "Product Announcement" which is dated January 10,2007, a heading states "Retirement of J# language and Java Language Conversion Assistant from future versions of Visual Studio", and here is the text under that heading:
Since customers have told us that the existing J# feature set largely meets their needs and usage of J# is declining, Microsoft is retiring the Visual J# product and Java Language Conversion Assistant tool to better allocate resources for other customer requirements. The J# language and JLCA tool will not be available in future versions of Visual Studio. To preserve existing customer investments in J#, Microsoft will continue to support the J# and JLCA technology that shipped with Visual Studio 2005 through to 2015 as per our product life-cycle strategy. For more information, see Expanded Microsoft Support Lifecycle Policy for Business & Development Products.
My question is what is the future direction of the LiveLink SDK? Is it now being actively developed, and will it continue to be actively developed in the future. Will this dependency on MS J#, a "retired" Microsoft tool, be removed in favor of an actively developed tool? When could this be expected to happen?
I'm currently evaluating whether the LiveLink SDK is a viable option for inserting documents into LiveLink directly from a .NET application, and this existing dependency has me leaning towards "NO" as the answer. Any information would be appreciated.
