Windows Vista - the impact on developers

By Alun Williams

Posted on 30 Jan 2007 at 12:51

Note that you can still use unmanaged code - such as traditional C or C++ languages - to develop WPF applications. You could call .NET code from such languages in order to get the interface rendered, pointed out Moulster. 'So while you should expect to write managed code to make the full use of the Windows Presentation Foundation you could certainly call that code from unmanaged code,' he said.

When it comes XBAPs (XAML browser applications), which use WPF running in Internet Explorer, you are tied into IE6 or 7. What Microsoft has rather cleverly done is to use WPF as the same technology for both native Windows interfaces and Web browser interfaces. What this does is make it easier to integrate IE into the application stack. When the desktop extends out to the Internet, a common metaphor for the development of Windows and integrated search, developers will inevitably be lead towards Internet Explorer - Mozilla or Opera will not be equivalent options for end users at all.

Getting away from the interface, Moulster gave other instances of the impact of Vista on development issues, for example, digital identity management through the use of Card Space. Not forgetting security and the impact of User Account Controls, in particular.

Finally, Moulster noted that developers should not need admin rights for development purposes alone with Vista, reducing conflicts over user privileges for the resulting applications.