BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage .NET Content on InfoQ

  • Breaking Changes Planned for .NET 4.5

    The actual version number for .NET 4.5 assemblies is 4.0.30319. If that looks familiar it is because that is also the version number for .NET 4.0 assemblies. Much to the chagrin of developers, Microsoft will be updating core assemblies “in-place” despite the fact that it includes breaking changes.

  • There Will Be No Metro UI for Mono

    Miguel de Icaza said that Xamarin won’t port Metro to other platforms, one of the reasons being Linux’ failure on the desktop. .NET developers interested in writing cross platform apps will be able to do so using Mono for the business code and rewriting the UI code for each platform.

  • ASP.NET MVC Pipeline And Extensibility

    ASP.NET MVC is designed with extensibility in mind and almost every part of processing pipeline is extensible using your own providers to replace the standard implementation. Simone Chiaretta, in his blog post “An Introduction to ASP.NET MVC Extensibility” gives an introduction to various stages in the ASP.NET MVC Pipeline, and a brief explanation of how extensibility comes into picture.

  • Windows Share, a New Data Exchange Mechanism in Windows 8

    Microsoft has created a new mechanism for sharing information between applications in Windows 8 called Windows Share. Apps can share text, bitmaps, HTML, URI, files, and other type of data, and the usage scenarios are numerous. For example, the app receiving the information can post it to Tweeter or Facebook make it easy to post information to a social network without actually visiting it.

  • Design Details of the Windows Runtime

    The Windows Runtime (WinRT) was created to provide a fluid and secure application experience on Windows. WinRT was influenced by both .NET, C++ and JavaScript. WinRT does not replace the CLR or Win32, but rather provides unified support for applications written in different languages to run on Windows using the new Metro UI.

  • F# 3.0 – LINQ + Type Providers = Information Rich Programming

    Microsoft recently announced a developer preview release of F# 3.0 – new features include LINQ-support through Query expressions and a Type Provider System along with a set of built-in providers that allow succinct programming against a variety of data sources.

  • C#, VB.NET To Get Windows Runtime Support, Asynchronous Methods

    C# and VB.NET will soon be getting new features like Windows Runtime Support, Asynchronous Methods, Caller Info attributes and more. Also, compiler will get APIs which will expose what the compiler knows about the code to the IDE and the developers.

  • Designing Loosely Coupled Metro Applications with URIs

    Protocols allow applications to launch other applications using URIs much as you would launch a website. This allows you to build a collection of small work-flow centric applications that work together seamlessly.

  • Application Lifecycle Management in Team Foundation Server 11

    Team Foundation Server 11 has added many features in the area of Application Lifecycle Management. Some of the highlights include support for code reviews, iterations/sprints, resource allocation, third part testing frameworks, and a much more capable dependency graph.

  • Visual Studio 11 Preview is Now Available

    The Visual Studio 11 preview is now available for MSDN subscribers with a general release planned in the next few days. Here is a brief summary of the features they are showing off at Build.

  • C# and Visual Basic on the WinRT API

    While Win32 APIs can be called from .NET languages, doing so can be quite difficult. So for the last two year Microsoft has been building a replacement known as Windows Runtime or WinRT with cross-language support in mind. WinRT components can be created in both C++ and .NET and may be consumed by both of those as well as JavaScript.

  • Microsoft has Abandoned Silverlight and All Other Plugins in Metro IE

    Though it has been hard, we have been trying to avoid reporting on rumors about the death of Silverlight for quite some time. As in all things, rumors tend to be exaggerated or out-right false. Unfortunately the end of Silverlight is no rumor; if Microsoft doesn’t change course it, as well as Flash and other plugin technologies, will be effectively unusable when Windows 8 is released.

  • Build Sessions to Watch For

    With 274 sessions at the //Build/ conference it is hard to predict which are going to be important and which are just filler. Here is a rundown of the sessions we think are going to be important to enterprise developers.

  • WinRT: An Object Orientated Replacement for Win32

    WinRT is a modern OS-level API that is built upon the Windows kernel. It isn’t just a layer on top of Win32, it is a replacement for it. Built with Object Orientated concepts such as a unified type systems and reflection, it is equally usable from C++, .NET, and dynamic languages such as JavaScript.

  • Major UI Themes in Windows 8

    Windows 8 Metro doesn’t just change the way applications look, it fundamentally changes how they behave. Applications will no longer be running in the background at all times, they will be suspended whenever they are not view. Rather than a save button, most applications will be constantly updating data on the cloud so that the user can seamlessly switch from one device to the next.

BT