Showing posts with label Windows 8. Show all posts
Showing posts with label Windows 8. Show all posts

Tuesday, February 19, 2013

What Every Developer Needs To Know Now


As developers we live in interesting times. The advent of Windows 8 has changed the landscape for many developers and the move from the desktop to tablets and mobile presents even more challenges. We turned to Dave Wheeler, the keynote speaker at next month's DevWeek for help and advice.



"...developers need to take on board the fact that the computing ecosystem is changing. Windows 8 is a wake up call to developers that change is coming: the exact pace of that change is up for debate."

What are the new and important technologies being introduced or highlighted at this year's DevWeek?
Windows 8 has to be the most important, but as we had a fair idea of what was coming in 2012 it can't really count as new. Even so it will be in the limelight throughout this year's conference. Similarly, we’ve known about HTML 5 and CSS 3 for a while. As a client developer, these are the obvious areas to focus on.
There are some fun novel areas to take a look at, such as functional programming, Roslyn, Rx and SignalR, which it would be easy to overlook. And there are some interesting talks on technologies such as PhoneGap (AKA Apache Cordova).
My tip to anyone attending DevWeek would be to choose at least one talk that’s outside his or her normal area of work: you never know what it might trigger.

How does Windows 8 change the Microsoft programming ecosystem?
Not at all, for the majority of corporate developers.
Clearly, developers that are targeting home users will consider embracing Windows 8 Store Apps. However, I’m forecasting that the vast majority of usage of Windows will continue to come from traditional applications that work across the range of Windows XP, 7 and Windows 8.
Which means that they will be continue to be developed in classic C++ and .NET.
However, developers need to take on board the fact that the computing ecosystem is changing. Windows 8 is a wake up call to developers that change is coming: the exact pace of that change is up for debate.

What are the most important things that developers need to understand about developing for and in the Windows 8 environment?
It’s different, in every way.
Many developers are simply not used to designing applications that work on low-power devices, which are driven through touch, and which run under such stringent platform constraints.
They’re not used to dealing with the Application Lifecycle Model, monetizing applications through advertising or in-app purchases, and which work on the different form-factors.
So it is not just a new API for writing Windows applications: the shift in thinking that is required is as great as that in moving from desktop Windows to iOS.
Of course, the good news is that developers can work with languages and tools that they are familiar with, thus making the transition as painless as possible.

Given the prediction that users will increasingly move from the desktop to mobile devices, how best should .NET programmers protect themselves from the future?
The best solution is to win the lottery! Or become a plumber.
More seriously, though, .NET is still an excellent platform for developing on mobile devices, with support via Mono on Android and iOS/OSX, and with great support on all flavours of Windows. .NET remains an excellent server-side technology with ASP.NET MVC, and WPF is still the best technology for building robust, complex desktop applications.
So there’s absolutely no need to rush off to another technology just yet.
Whilst it is easy to assume that HTML is the “better” technology for working across the different devices, anyone who has tried to build an app that looks good and works well in HTML will realise that it is non-trivial.

"Clearly, there are fad technologies that might be “hot” right now, but the key to being a good developer is having a breadth of skills, and excellence in a few key areas such as OO principles, testing and knowledge of the entire software development lifecycle."

And what technologies are vital to learn to ensure a successful future?
There is no one technology. Developers are still maintaining systems written in C on Windows, so there is scope for a good career across a range of technologies. Clearly, there are fad technologies that might be “hot” right now, but the key to being a good developer is having a breadth of skills, and excellence in a few key areas such as OO principles, testing and knowledge of the entire software development lifecycle.
As much as anything, developers need to ensure that their other skills are in good order: their ability to contribute to teams; their attitude; their business awareness; their professionalism and their willingness to learn.

Finally, can you give us your impressions of DevWeek for those anybody who hasn't attended it
One of the great things about DevWeek is that it encompasses so many different areas of development, design and architecture. When I used to attend as a delegate, and it was much smaller then, I always used to find it a challenge as I wanted to see nearly all the talks! And now its even larger that must be even more of a problem.
What hasn't changed is that it's still a laid back, informal conference where the speakers don’t disappear from sight and  there’s lots of opportunity for an informal chat, preferably over a drink, as well as the many breakout sessions.

Source: I Programmer

Thursday, May 17, 2012

Embarcadero Announces Support for Windows 8 Metro Development with Release of Embarcadero Prism XE2.5


Cross Platform Flexibility Enables Rapid Development of Desktop and Mobile Applications for Windows 8 and Windows 8 Metro

Embarcadero Technologies, a leading provider of software solutions for application and database development, today announced the availability of Embarcadero Prism XE2.5, the cross-platform .NET Pascal development tool for rapidly developing .NET, Mono, and ASP.NET applications for Windows(R), Linux(R) and Mac OS X.

The latest release of Prism, which is also included as part of RAD Studio XE2, extends the reach of software developers with support for both Windows 8 and Windows 8 Metro application development and also supports the latest beta of Microsoft Visual Studio 11.

"Prism XE2.5 delivers the ability for developers get a head start building Metro applications for desktop and mobile today, while Windows 8 is in the beta preview stage," said Michael Swindell, Senior Vice President of Marketing and Product Management for Embarcadero. "It's Embarcadero's goal to provide developers with the best development solutions to leverage common skills and code deploying to Windows, iOS, Mac, and the Web. We're excited about Prism XE2.5's ability to help developers get ahead of the curve with Windows 8 and Metro development."

With the upcoming release of Windows 8 comes the new Windows Runtime (WinRT) API stack for creating visually stunning touch-enabled Metro applications. Prism XE2.5 provides experimental support for developing Metro apps and for working against the WinRT APIs, based on the current Consumer Preview of Windows 8.

"Embarcadero Prism and the Oxygene language continue to lead the way with innovative language features and support for the latest .NET Framework and Windows," said Jim McKeeth, Developer Evangelist at RemObjects Software and host of the Podcast at Delphi.org. "Version 2.5 is a huge leap forward with support for Windows 8 Metro style applications and the Windows Runtime. I know developers are excited to develop apps for the newest version of Windows."

Other key features include:
1. Flow Control Analysis: The Oxygene compiler in Prism XE2.5 has been extended with an enhanced flow control analysis infrastructure that analyzes your code beyond the basic compile.

2. Await: The Oxygene language in Prism XE2.5 introduces the "await" keyword, which allows users to unwrap asynchronous calls and write linear code that can use or build on the results of asynchronous operations.

3. Mapped Types: Oxygene 5.1 in Prism XE2.5 adds support for an exciting new language concept called "mapped types," which are virtual classes or interfaces that map to existing types in the framework or your own code, exposing them with a different API.

Monday, April 23, 2012

Visual Studio 2011 and Windows 8 for Metro style Apps for .Net Development


Windows 8 & Visual studio 2011 includes some new features that help .Net developers and ASP.Net developers for their .net development. Here we will explore Windows Runtime that can be designed for developing Metro Style Apps for .net developers who are expert in Unmanaged C++, JavaScript and .Net.

Windows Runtime (WinRT)

Metro Style Apps can be called one the coolest features in Visual Studio 2011 and Windows 8. For getting access to templates for Metro Style App the initial step would be to install VS2011 developer preview on Windows 8 Developer Preview. Windows Runtime (RT) handles these apps and RT is designed for easily developing metro style apps using the expertise of Asp.net developers.

For developing web application .net developers can use HTML 5, CSS 3 and JavaScript. For accessing rich hardware functionality Javascript calls WinRT system.For developing Metro style applications .Net developers can make use of extensible application Markup language (XAML), C#, VB.NET.

Windows check all the access rights to the user data and system resources for programming with WinRT. Package Manifest specifies these access rights. The Metro Style application needs to send a quick response to the end-user and for this apps use Asynchronous operations.

As per Microsoft’s definition “Metro style apps are full screen apps tailored to your users’ needs, tailored to the device they run on, tailored for touch interaction, and tailored to the Windows user interface.

Windows helps you interact with your users, and your users interact with your app”

How to create Metro Style Apps using C#?

Step 1: Open VS2011 and create a new Windows Metro Style App as below:

You will receive below project structure after creation of application:

Step 2: You need to double click on ‘Package.appxmanifest’ for viewing the settings of application as below:

You will see information for the “Application UI” e.g. Logo as shown in the above image. Also note the size restriction for the Logo image.

Step 3: By clicking on the Capabilities tab you will get the List of System Features that the application can use.

Step 4: Click on the ‘Declaration’ Tab and by using this tab, you can add declarations for the application:

The packaging tab also allows developers for defining properties that identify and describes the package for application at the time of deployment.

Step 5: Add a new class file in the MyApp application and name it as ‘DataClasses.cs’. Below are the classes you need to add in it:

Step 6: Open MainPage.Xaml then add a ListBox and use the Databinding expression as shown below:

Step 7: By running the application you will get output in the Emulator as follows:

You are finished with it and we saw how WinRT can be used for developing Metro Style Apps by .Net developers.

Tuesday, April 17, 2012

Announcing Windows Azure Media Services


Windows Azure Media Services is a cloud-based PaaS solution that enables you to efficiently build and deliver media solutions to customers. It offers a bunch of ready-to-use services that enable the fast ingestion, encoding, format-conversion, storage, content protection, and streaming (both live and on-demand) of video. It also integrates and exposes services provided by industry leading partners – enabling an incredibly deep media stack of functionality that you can leverage.

You can use Windows Azure Media Services to deliver solutions to any device or client - including HTML5, Silverlight, Flash, Windows 8, iPads, iPhones, Android, Xbox, and Windows Phone devices. Windows Azure Media Services supports a wide variety of streaming formats - including Smooth Streaming, HTTP Live Streaming (HLS), and Flash Media Streaming.

One of the unique aspects of Windows Azure Media Services is that all of its features are exposed using a consistent HTTP REST API. This is true both for the media services we've built, as well as the partner delivered media services that are enabled through it. This makes it incredibly easy to automate media workflows and integrate the combined set of services within your applications and media solutions. Like the rest of Windows Azure, you only pay for what you use with Windows Azure Media Services – making it a very cost effective way to deliver great solutions.