Will WinFX, Longhorns new programming interface, look sufficiently familiar to experienced Windows programmers?
Well, anyone who has worked with managed code will see that WinFX is taking APIs (application programming interfaces) and doing them in a very consistent, rich way for managed access. Anyone who has seen the .Net framework will see this as an evolution of that. There has been a switch in the last four years toward using managed code. I’d say maybe half of the stuff that gets done now is in managed code. So that just pushes this a little bit further. On my last slide (at Monday’s keynote) I had five action items: fundamentals, which are all of the things around security and updating and managed code; use managed code; use Web services; take advantage of the rich client; and, finally, get involved in the Windows communities that will really shape what we end up doing in Longhorn. Can you talk a little bit about how some other Microsoft systems and initiatives, such as Xbox, embedded systems, Tablet PC, etc., fit into the Longhorn scenario? Tablet came out a year ago. We have over 400,000
Related Questions
- After drinking Maxmyer NanoCalcium, why some people experienced rashes appeared all over the skin that look very much like lupus and are itchy?
- How can I redirect PETScs stdout and stderr when programming with a GUI interface in Windows Developer Studio?
- What is Windows Shell application programming interface?
