JNBridge is a technology that allows Java and .NET code to share objects without relying on cross-compilers. Under this scheme, the JVM and CLR may be running on the separate machines, separate processes on the same machine, or even in the same process. With JNBridge 5.0, these capabilities have been extended to also support each platforms native transaction support.
Assemblies built in Silverlight 2 and 3 are not binary compatible with the .NET Framework, so if you want to share code you need generally need to dual-compile. With Siverlight 4 and .NET 4, you will be able to use some Silverlight-based assemblies from within .NET 4.
Visual Basic for Applications is a dead-end and Visual Studio for Applications isn’t ready for prime time, leaving developers in the uncomfortable position of trying to mix .NET code with legacy VBA macros. Fortunately Visual Studio Tools for Office makes it relatively painless.
Microsoft has announced the release of a number of tools for Eclipse: Windows Azure Tools for Eclipse, Windows Azure SDK for Java, Eclipse Tools for Silverlight, plus a facelift for Eclipse to look-and-feel like Windows 7.
Noelios Technologies, the France-based consulting services firm, is shipping a new version of the Restlet open source project, a lightweight REST framework for Java, that includes the Restlet Extension for ADO.NET Data Services. The effort is a collaboration between Microsoft and Noelios Technologies and it makes it easier for Java developers to take advantage of ADO.NET Data Services.
The “Windows API Code Pack for Microsoft .NET Framework” is a wrapper that exposes Windows functionality to .NET developers. The wrapper is written primarily in C#, with the DirectX functionality in C++/CLI. The source code is available, but it isn’t licensed as open source.
Rama Pulavarthi, member of the Java Web Services group at Sun Microsystems, has reported on the availability of the JAX-WS 2.2 and Metro 2.0 nightly builds. JAX-WS 2.2 is mainly aimed to add support for WS-Addressing 1.0 - Metadata specification and Metro 2.0 is scheduled to be delivered on GlassFish v3.
Luca Bolognese has reimplemented Excel’s collection of financial functions in F#. Released under an open source license, it should prove useful for both learning F# and for porting applications from Excel to .NET.
Ja.NET is a port of Java 1.5 SE to the .NET platform. Ja.NET is built on top of noteworthy open source projects such as the Eclipse JDT compiler, Mono's Cecil, and Apache Harmony. Unlike IKVM, which is a full JVM running on .NET, Ja.NET compiles directly to IL. This should give it a significant advantage in performance.
IBM, Oracle, Red Hat and others have just announced the formation of the Web Services Test Forum, a venue for continuous testing of interoperability for heterogeneous Web Services implementations as well as a flexible way for vendors and customers to define the interoperability scenarios that are important for them. But how does this relate to WS-I and why has Microsoft not signed up to it yet?
In an unprecedented move, Microsoft is giving all the CPAN authors access to an array of hosted Windows virtual machines. The machines will be hosted in Australia by a third part with the goal of making it possible for Perl on Windows to achieve parity with Perl on other platforms.
Using tools like Greasemonkey, users are able to extend many web applications whether or not the site owners want them to. With Crack.NET, that same level of user control can be achieved over WinForm and WPF-based .NET applications.
Using Visual Studio Shell as a starting point and Mono as a runtime, Embarcadero Technologies has introduced a new version of Delphi for .NET called Delphi Prism. This project is being target towards cross-platform developers who want to bring the .NET ecosystem with them to OS X.
From the beginning, the .NET stack had first class support for unmanaged libraries. By using P/Invoke one can access most of the Win32 API and support for COM opens up developers to a wealth of applications and third-party libraries. But should .NET developers actually take advantage of this?
Microsoft Corp. joined the Advanced Message Queuing Protocol (AMQP) Working Group, an organization focused on the development of the AMQP specification.