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.
Believe it or not, C# is going to have full support for optional and named parameters. This, and other features intended for COM support, will be included in C# 4. There was also a rumor about parameterized properties.
In .NET 4 types will no longer be restricted to a single assembly. A single type, or part of a type, can be extracted from one assembly and placed into another. Why would you do this? Well first off all, to reduce the cost of including the Office Primary Interopt Assemblies from several megabytes to about 2KB by only including what you actually need.
In conjunction with Attunity, Microsoft has released SSIS Connectors for Oracle and Teradata.
Robert Bell, Microsoft Solution Architect, introduces interoperability scenarios for using Silverlight from Java and provides architectural guidance using sample code snippets.
AMQP came from inside of JPMorgan, thanks to John O'Hara. But his vision was bigger than just a new way to do things internally. The standard and open source technologies around it have been gaining momentum. Jeff Gould and others shed some light on where AMQP came from, who is driving it, and where it might be going.
Ted Neward points us towards a solid piece by Bruce Wilson about increasing the power and usability of enterprise applications by using Microsoft Office as your client instead of a browser. And as Ted points out, this strategy can be a great option even if your backend is Java or any other Web Service aware platform.
The latest interoperability event (a “plugfest”) at Microsoft’s Redmond campus showed impressive results for interoperability between future releases of Sun’s Metro Web Services and Windows Communication Foundation in .NET 3.5. InfoQ had a chance to talk to Harold Carr, the engineering lead for enterprise web services interoperability at Sun, about the interop results.
When it comes to web services interoperability between .NET and Java, the choice used to be limited to SOAP over HTTP. Two new options recently became available in this area: WebSphere MQ (WMQ) and ActiveMQ transports can now be used for building interoperable web services between Java and .NET.
Microsoft switches from the Web Structured, Schema’d & Searchable (Web3S) protocol to Atom Publishing Protocol (AtomPub) for services offered by Microsoft's Live Platform on the Web.
With the release of Java 6 and JSR 223, developers now have the option of being able to have inter-operability between Java and any of the supported scripting language. Mark Fortner has been exploring the capabilities of the Bean Scripting Framework (BSF) with JSR 223, and has found a number of items that could be improved.
Currently Mono offers two GUI toolkits, Windows.Forms and Gtk+. Both of these work on OS X, but they only run via an X server. Just like early Java GUI toolkits, the non-native look and feel is causing problems for developers. Miguel de Icaza has announced that Mono 1.2.6 will be shipped with an OS X native backend for both toolkits.
Today JNBridge, one of the leading suppliers of Java/.NET interoperability tools for software developers, announced the release of two new Java Messaging Services (JMS) Adapters for the Microsoft .NET platform.