Microsoft’s New Developer Tools{3}


by Cary C
Microsoft is gearing up to release a new slew of technologies that help developers create server based apps.  All of the products mentioned in the article are currently in their beta releases and are anticipated to be released within the next year.  The trio of tools has been designed with flexibility in mind, as more and more applications are used not only on a traditional web based page that are viewed on computers, but also need to be visible using mobile devices.  With mobility in mind, the applications that are going to be built using Microsoft’s new developer’s tools will be designed to be very lean.  Because of this, Microsoft has built in tools that will allow the developers to find similar code within their applications and consolidate said code to create a more reduced package.  Microsoft’s focus is to continue to have developers use its products to create applications using .NET, but they are also moving away from their traditional dependence of presuming that all users are going to want and can use Internet Explorer for their applications.

While I am not a developer, nor do I plan on becoming one in the near future, I am interested in learning where Microsoft is heading with its developing platforms as it is my job to ensure that the hardware and underlying Operating Systems remain stable and are usable.  MS appears to be interested in having their developers host applications using MS Azure which assists end users in their access to browser independent applications.  I have never understood why MS for so long has chosen to base their products on the assumption that you will use Internet Explorer.  While I do not have anything against IE itself, nor do I have any problems with MS’s policy that IE is installed by default on Microsoft Operating Systems, I prefer other browsers.

Microsoft is using their old tricks of doing their best to integrate all of their products into an extremely large suite of applications.  I have watched MS do this for well over a decade.  The classic example is that they will release a new server application, such as their email application (Exchange), but a user will not get the full benefits of this application unless they also purchase the newest release of the client side application (Outlook) which will benefit from all of the features available on the server.  I think this is a very solid business plan since it keeps both the client and server side in a state of relatively constant upgrades, or at least it keeps some people upgrading every two years or so.

 

Reference:

Miller, M. (2011, Sept. 14th). Build: Creating Server Apps with Windows Server 8, Azure, and Visual Studio 2011. PC Mag. Retrieved from http://forwardthinking.pcmag.com/show-reports/287761-build-creating-server-apps-with-windows-server-8-azure-and-visual-studio-2011