Intallation of JLCA 3.0 Beta on Visual Studio .NET 2003

While installing the JLCA 3.0 beta release for Visual Studio .NET 2003, we have heard back from some customers that there are errors such as the following being thrown “The VJU.EXE Process ended unexpectedly”“Microsoft.JConvert.Extensions.dll not registered. Please reinstall the JLCA”“Conversion failed:  Main engine couldn’t be instantiated due to Security restrictions or setup problems” The reason…

2

Moving from JDBC to ADO.NET

One of our customers who wanted to move from JDBC to ADO.NET wrote to us that he was unable to find any article, white pages or case studies about migration database applications from java to .NET i.e. JDBC to ADO.net.  He wanted help in finding the relevant information. A> Data access technologies have been continuously…

0

Accessing Java Objects from within C#

We often hear back from customers regarding this interesting problem. I am just throwing a perspective on this. Here is what we heard from one of our customers: I’m trying to get my organization to move to C# as the primary development tool, but I have to work with another group who insists on using…

2

Availability of JLCA with Visual Studio Express SKUs

The Java Language Conversion Assistant tool is not available as a download with the express editions of Visual Studio 2005. You would need to install Visual Studio .NET 2003 or Visual Studio 2005 to use Java Language Conversion Assistant. For Visual Studio 2005, the JLCA tool is available with the following Visual Studio SKUs    – Visual…

4

java.lang Vs primitive types (i.e. int vs java.lang.Integer) in J#

Here are a set of questions that one of our customers asked us recently. They were concerned that our library is not friendly to Java wrapper types (java.lang.Integer, java.lang.Character, java.lang.Boolean and so on). They asked us to explain. Q>  Why supporting primitive types as int, bool as well as their arrays is not enough in…

1