Open-source .NET gets AJAX polish
Components punch
Agentless Backup is Not a Myth
The open-source implementation of Microsoft's .NET development framework is getting some AJAX spit and polish from interface specialist Telerik.
Telerik, which builds re-usable software components and is a partner of Microsoft and Borland, has announced that its RadControls for ASP.NET AJAX now supports Mono.
This brings a suite of controls to the Novell-backed implementation of .NET spanning an AJAX data grid and HTML editor.
As a result, a suite of off-the-shelf, re-usable interface components that have been refined for Windows are now available to developers working on Linux and Unix with Mono. Telerik's components are used by major customers that include NASA, Boeing, Vodafone, and Microsoft itself.
Miguel de Icaza, Mono's lead and also the creator of Gnome, said on his blog that Telerik had helped the Mono team by providing access to their source code, test suite, and their Q/A team to help ensure that the company's "thousands of tests" ran as well on Mono version 2.4 as they do on the official .NET implementation from Microsoft for Windows. Testing has been conducted during the last few months.
Telerik said it was optimistic about the effect its partnership with Novell will have on the industry and the "benefits" it will bring to .NET developers.
Mono's been active for eight years, and was started in response to the then-new .NET from Microsoft as a way to bring the development benefits of that framework to Linux and Unix. ®
Regcast training : Hyper-V 3.0, VM high availability and disaster recovery
COMMENTS
Compatible until MS breaks it
Lowering the friction required to move apps from Windows is one way to ease the process of selling Linux to managements as a viable server host.
Microsoft know this. I suspect this 3rd party has been a lot more helpful to Mono's developers than MS have, beyond selling them a set of manuals.
MS have know for decades that controlling their interfaces (and choosing when and how they change them) is a key tool to stopping anyone moving. A frozen interface is a copyable interface and hence offers potential for migration.
If they do see re-hosting (IE windows licensing from big users drops as they re-host) expect the usual MS responses. MS can innovate (well they can buy someone who can innovate) when they want to. Expect a new .Net spec with some new features (probably ones developers have been clamouring for for years) and some pointless stuff which will waste developer time all with various parameter orders shuffled but which will break Mono quite effectively for some time.
Mine will be the one with various inside Microsoft books in the pockets.
Not more Mono crap
Stop pissing around with crap like Telerik and get one with actually implementing the .Net interface. No wonder most of the code is just stubs if they are wasting their time on crap like this.
Still, I guess it explains a lot of Gnome issues. He must have aimed for style-over-substance there too.
Sorry, Miguel
While I admire Miguel's skill as a software developer, it seems that he's either very naive (or disingenuous) in his summary dismissal of the community's well-founded concerns about the dangers of Microsoft's shared source license and refusal to guarantee access to the .NET patents.
IT infrastructure monitoring strategies
Agentless Backup is Not a Myth
Top 10 SIEM implementer’s checklist
Steps to Take Before Choosing a Business Continuity Partner
Enabling efficient data center monitoring
