Windows 8 - What is the future of WPF applications?

    General discussion

  • Microsoft introduced the "Windows 8, " and if I do not get it wrong it looks like Microsoft is betting big on applications in html5.

    But what about WPF and Silverlight?

    Microsoft will abandon them?

    Or will html5 and WPF have different purposes?

    Should I invest in learning WPF or wait to see what direction it will take?
    Thursday, June 2, 2011 9:04 PM

All replies

  • BladeRunner2019,

    I cant speak for microsoft on the point of Html5, nor if WPF and Silverlight are headed for the dumpster. But i don't think its something that anyone needs to worry about.

    Speaking from a developers standpoint i think its wise not to rat hole yourself into any single technology. Many people don't last long as developers because they learn a single technology and refuse to learn new things, this forces them into a bad situation and they become less valuable in the marketplace. There is no rule against learning to develop using multiple platforms, including learning both WPF and HTML5, knowledge in one area almost always helps you in another.

    Having said that, there is also great value in becoming an expert in a particular technology. HTML5 is still being developed along with all of its associated pieces but it has a lot of people excited (including me), it will undoubtedly become a key technology for the future. WPF has been around for about 5 years and Microsoft has been largely silent on its future and this has been disconcerting to many developers. 

    So all that all i can say is WPF is a cool technology and i have enjoyed developing (and continue developing) on the platform, HTML5 looks awesome and i look forward to learning and developing on it as well. I'm sure the day will come that WPF and Silverlight will no longer make sense as technologies, but who knows how long that will be, for now i will use the best tool for the job.


    Friday, June 3, 2011 2:56 AM
  • At the last PDC, the Silverlight folks were shocked to hear that HTML5 is going to be king.  In fact just about a month ago MSFT announced that Silverlight is now primarily a Phone application, and that the future is HTML 5.  Don't believe me, just head over to the Silverlight site....

    We've heard very little regarding the next version of WPF.  So is that because MSFT's internal direction has changed?  I don't think we know.

    If HTML5 becomes the defacto Windows development platform, I think a lot of folks will have felt "left in the dust" by MSFT.  How that could happen is beyond me.  I think MSFT will continue WPF but it will become one of those proprietary things that all "open" developers will hate.

    Too bad MSFT couldn't make WPF as popular and effective as HTML5 and JavaScript.  JavaScript to me is the most arcane idiotic language on the planet today.  I absolutely don't like it.... Compared to WPF and C# it doesn't hold a candle except for one thing.  It has intrinsic DOM support that is stable.  Unlike MSFT latest regression into HTMLDOCUMENT support being primarily through the MSHTML classess, which by the way are all on the COM side and poorly documented for C# people.  So in a sense Javascript wins because of DOM, but that's it.


    Friday, June 3, 2011 3:56 AM
  • JavaScript to me is the most arcane idiotic language on the planet today.  I absolutely don't like it....  


    Today? Try ever.  I've used a ton of languages over many, many years and I can't thnk of any that are as bad as Javascript.  Heck, I think I enjoyed using compiled BASIC more.  

    You are right--the only reason Javascript didn't die years ago is the fact that it has always been the only thing tied into the DOM.  There is no reason that a real language couldn't be in there, except that for some reason the browsers decided to standardize on freakin' JavaScript. 

    Friday, June 3, 2011 4:36 AM
  • At the last PDC, the Silverlight folks were shocked to hear that HTML5 is going to be king. 





    No "they" didn't.  Some people decided that something one person said could possibly be interpreted in that way and got a bit carried away.


    Friday, June 3, 2011 10:21 AM
  • MS is showing off something which will run on tablets.

    I wouldn't extrapolate from that too far.


    What will probably happen is that WPF and Silverlight will eventually converge somehow.

    Silverlight is used for more apps than WPF and getting more attention but both are being developed.

    They're similar at the moment and getting more so.

    Learning one or the other or both is a good idea IMO.


    MS would be a bit crazy to be developing Silverlight and WPF 5 if they were going to drop the products.

    Friday, June 3, 2011 10:27 AM

  • Andy;

     And since then Scott has been reassgned duties.  I was hanging out on SL site for months and heard all the chatter.  MSFT is silent on SL future.  Release 5.0 was nothing.  MSFT also redirected it to be "The mobile phone application language".   SL is too restrictive and is NOT a good application language as a result.  Sure you can create OOB applications but why would anybody choose that over WPF?  WPF is unrestricted so really it is the only true managed application facility MSFT has, unless one wants to revert to Windows forms.

    MSFT has subcombed to HTML 5, period.


    Friday, June 3, 2011 8:17 PM
  • I think it is a great idea to learn WPF today since the model for the web applications is very similar.  Have you seen the "Knockout" stuff for HTML5/JavaScript/JQuery/etc...?  There is a tremendous amount of overlap in the programming paradigm with WPF/SL.  You still have MVVM.  Styles are like CSS.

    I know there has not been an announcement for a Blend 5 and I've seen enough chatter to guess they are planning a single tool that will be able to generate WPF, SL, or HTML5 code.  I see these worlds as merging and you'd be better off learning WPF today to help you to understand the new models coming out.

    Friday, June 3, 2011 10:33 PM
  • Great comments!
    The debate on this subject is great. The post is still open to new comments.
    Friday, June 3, 2011 11:23 PM
  • I agree with Jeff WPF is far superior to HTML 5 and CSS / Javascript.  Go for it.  You can always pick up SL when you thing you want it...  but be ready for disaapointment coming from WPF world.

    Saturday, June 4, 2011 3:50 AM
  • The concept of WPF was taken from Adobe flex (xml markup usd to define and design the UI) which uses Action Script for the code behind. WPF uses C# for the code behind and Android uses Java for the code behind. All three code behinds are very similar in syntax and all three XML UI front ends are very similar. I have been developing in all 3 over the past few years. The architecture is advanced and sound. Microsoft can't abandon it, they may morph it a bit but the framework structure will remain the same. I wouldn't worry too much.

    As far as silverlight goes I can't see them abandoning that as adobe's flash would take over. HTML5 and javascript are great but you can't abandon silverlight and flash which are advanced rendering frameworks that have oodles of methods to make animation easy to use.

    Monday, June 6, 2011 1:16 PM
  • One of the next big things coming along is Jupiter.

    That somehow involves xaml with C#/VB/C++

    It would seem there's also HTML 5 for widget/active tile thingummies.


    So whilst they may be renaming, converging technologies and whatnot, your xaml and c# knowledge is going to be good for some time yet.


    The problem is the nature of the panic driven blogosphere.

    It's in people's interests to stir up rumours and post dramatic headlines because it gets them traffic.

    It would be nice if MS adapted to this and published roadmaps earlier.

    But they don't.

    The sky isn't falling until my blog says it is ;^)

    Then of course you better click on all the advertising to hold it up.

    Wednesday, June 8, 2011 10:12 AM
  • As technologists I think it is important we remember that change is a good thing, it keeps us all in a job and keeps us well paid.  Is it painful sure.  When I started developing in Silverlight and WPF with MVVM I thought my head was going to explode.  It was such a drastic paradigm shift I didn't think I would ever become fluent in it.  Guess what, I did and now I love working with it.

    Now, do I think WPF is dead? No.  Do I think HTML5 is the future? Yes.  So are quantum computers but I am not expecting Q-Linq any time soon.

    My major concern with switching everything to HTML 5 is that JavaScript is still JavaScript.  It is not type safe, it is not compiled, and it hasn't had a major update in years.  Don't get me wrong, I think the advent of J-Query is awesome.  I use it heavily in all of my web based applications.  But it is not an update to the JavaScript language, just an add on.  In order for HTML 5 to be an effect method for application development I think the issues with JavaScript need to be addressed.

    I am more interested in seeing how Microsoft is going to provide HTML 5 Tooling for Windows 8 then worrying whether or not it is going to become the new defacto rich client development language.

    Anthony Terra
    Wednesday, June 8, 2011 1:07 PM
  • WPF tools are pretty bad, compared to other MVC tools like Apple's iOS.

    What I mean is, having to edit XAML by hand to do bindings is craazy....and makes me think they are not putting too much effort into it.


    I like C#, but I'd rather develop for iOS than deal with the XAML hell I've been in lately.



    Friday, July 8, 2011 10:35 PM
  • You can drag drop bindings in expression blend and to a lesser extent in the vs2010 designer.

    You don't have to edit them manually.

    Saturday, July 9, 2011 2:12 PM
  • How much does blend cost?


    Apple's tools are free, and the quality of them has improved greatly since iPhone popularity...


    MessageBox() ? Seems like you have to roll your own? I saw a blog on someone's implementation of WinForms MessageBox() API in WPF using MVVM. Must have taken the guy hours if not days. This is progress?

    Common guys, push back on this stuff. It's not fully baked.

    Tuesday, July 12, 2011 12:41 PM
  • You must of read an old blog.  MessageBox is now in the System.Windows.Controls library.  I would say the "not fully baked" is true for every bit of software out there in the industry.  I would also submit to anyone out there that VS2010 is the best IDE on the planet.  C# IMO is the best language on the planet as well.  My problem with .NET products is that they are still not true 1st class citizens on Windows platform.  In some cases Javascript get's better billing (within IE) than C# does.  Then when it comes to Office Interop, that's all a total joke...  We can't embed Office application windows into our .NET applications.   Something I've wanted to do for years to build specific targetted tools.  Can't do it...

    Tuesday, July 12, 2011 5:34 PM
  • XAML hell is real and long.  But once you get there you say, hmmmm, this is great!  Javascript hell is real, long and forever.  You never get there in Javscript.  I know nothing concerning Apple IOS but then again not a single computer in our organization uses Apple.  So in a sense, I'm safe.
    Tuesday, July 12, 2011 5:36 PM
  • Anthony;

     Agreed Javascript is a step back to 1970 programming and the very earliest models of Basic.  No typing, no reflection, just code it and go....don't look back, don't refactor, don't expect IDE to help you.  And most important don't expect much from debugger or to learn much from a debug session.  Try casting a Javascript object into a class to see parsed values while debugging a problem.  Or even simpler, try to see any value within the object.

    Tuesday, July 12, 2011 5:40 PM
  • Jupiter the big mysterious red dotted planet shrouded in toxic fumes pulling everything into it's orbit.  I guess we'll have to wait until September to find out but I think we're expecting it to be as big as the planet.  Wonder if MSFT will be able to deliver (with all the inter-departmental wars going on).
    Tuesday, July 12, 2011 5:42 PM
  • I don't think Silverlight will be abandoned.  But we don't know how it will be expanded either.  To me SL should become everything WPF is and not be a browser add-in.  The only line of demarcation for developing Web browser/Desktop applications should be whether they have a certificate or not.  In other words, even desktop applications should be allowed to be hosted fully in a web browser with no plug ins.  It then becomes the user's responsibility to validate the certificate of the product.  I never am amazed in wondering how Javascript became the default universal browser support language.  I know how it got there but I don't know why MSFT didn't trump this with a better .NET model FULLY supported in the browser.
    Tuesday, July 12, 2011 5:47 PM
  • Good points JP.

    Javascript and HTML are a pain to work with and XAML + .Net is a joy, streets ahead.


    A while back I did some work on chip and pin integration in Silverlight 4.

    I was somewhat irritated to find that on our dedicated machine ( it's literally a Till ) I had issues talking to another process via sockets.

    You have to serve a SecurityPoilicy.xml file from the machine to Silverlight before it can access a socket on the same machine.

    You can avoid that with a full trust out of browser SL app but the whole point is that SL had to run in a browser to connect a php served web page to local chip and pin.


    I think SL5 allows you to have trusted apps running in the browser and may well obviate this.

    So MS is edging towards fuller support in browser.


    I can imagine that MS might eventually offer the ability to write something which you can run with just a plug in if you want or full framework if you prefer.

    There again, I can imagine all sorts of things.

    Hopefully MS will have had time to consider the uproar from developers and give us some clear indication in September.

    Past experience tells me this is unlikely, but maybe someone somewhere is listening and thinking. 

    Wednesday, July 13, 2011 9:49 AM
  • Andy;

    Yes, I'm familiary with the XML policy files in SL.  The whole OOB thing in SL is a total mystery to me as that concept crosses over into Desktop world but WPF doesn't cross over into Webbrower.  SL Trusted web browser and OOB apps come no where close to WPF.  Reason: SL Class libraries just don't have full desktop support in them.  Example try parsing the HTMLDOM object in SL using MSHTML.  Can't do it. Period. Zilch. Nada. No how, No way.  The list goes on and on and on.  Or try this, in SL try to create a Richtextbox editor that allows you to paste in images (you know those picture thingys so new to the internet).  Ok so you figure out how to get them into the RTB control in SL, now try to save them to the back end.  The list is endless...   So what will be MSFT's answer?  Well it's looking like they are saying HTML5 and Javascript, but we'll see.  Turns out the C++ teams are tired of being 2nd rate citizens in the popular .NET world.  IE is C++ and well, now it will be the primary platform on Desktops?  Anyway that's what I've read concerning the internal department wars there, don't know if it's true or not.  I think all we are saying is this:

    1) Make .NET 1st class citizen

    2) Get rid of Office Intero and all of the other interops (Allow us to embed the fully monty into our applications)

    3) Make WPF fully supported in Browser using certificates to secure applications.

    • Edited by Mr. Javaman II Wednesday, July 13, 2011 12:41 PM Cowboy Coders Unite!
    Wednesday, July 13, 2011 12:40 PM
  • I'd recommend having a read of this excellent ars technica post before jumping to any conclusions re: Win8/HTML5/JS apps vs .NET/SL/WPF apps

    This is their conclusion (well lets hope it works out that way anyway...)

    > Far from being a developer disaster, Windows 8 should be a huge leap forward: a release that threatens to make development a pleasure for
    > native, managed, and Web developers alike. The unification of the .NET and native worlds; the full hardware acceleration; the clean, modern
    > APIs; Avalon as the primary solution for creating Windows UIs—this is what Longhorn's WinFX promised all those years ago, and this time
    > around it looks like it might actually happen.

    Seems like the whole HTML5/JS noise could be an attempt to attract non-MS web developers to the new platform

    Tuesday, August 9, 2011 5:51 AM
  • Let's hope, I quit a job once back in 2003 because they wanted to reclassify me as a HTML/JS developer and I wanted to migrate to .NET.  I would hate to find out I made a mistake :P.
    Anthony Terra
    Saturday, August 27, 2011 3:39 PM
  • You know that "C# will be used in writing immersive application or invoking a Jupiter-based application in Jupiter platform on Windows 8".  I suggest reviewing the following article:



    Monday, September 5, 2011 12:33 AM
  • Hi JP,

    Microsoft has delivered a new release candidate (RC) of Silverlight 5. Pete Brown, lead of the Developer Guidance Community Team at Microsoft in September 1, 2011, said the Silverlight 5 RC is a developer-only release that is aimed at getting developers ready for the final release later this year.

    Silverlight 5 performance has very good improvements include: Reduced network latency by using a background thread for networking; XAML parser improvements that speed up startup and runtime performance; support for 64-bit operating systems; and reduced network latency by using a background thread for networking.

    Please read the following article to learn more:



    Thursday, September 8, 2011 10:30 PM
  • Have you used expression blend to create your WPF applications? I usually use expression blend and Visual Stdio side-by-side to create my WPF applications. For binidings, I am not doing it manually. You can simply drag and drop bindings in MS expression blend. To learn more, visit the following link:

    I also suggest you to visit the following link to learn more about Silverlight 5 and future of WPF:


    Geof (MCSE+MCSD)

    Friday, September 9, 2011 5:15 AM
  • Hi Geof,

    Microsoft announced yesterday that Blend .Preview (which is Blend 5 .Preview version) is available now. I just posted a new article for this exciting news:


    Amir Ahani


    Friday, September 9, 2011 6:01 AM
  • Hello,

    well i dont think that HTML 5 + javascript(some hardware acceleration) is ready to fight against WPF = DirectX. Cammon i dont play games like old times but i see some DirectX 11 games and they look like movies. WPF will progress even more and i think the whole thing about HTML5 is a strike to the dead born Gooogle OS. MS is making great compitability everywhere and one way to do that is with HTML 5. I know many people who are open source fanatics and they will love HTML 5 but they will never use WPF only because it is microsoft. I hear before time that Mono project is now with close help from MS does this mean that MS is dropping windows as a marketplace i dont think so.

    Steve Ballmer before time said something about MS, i think it was on mix 2008 but it was like this Microsoft is what it is because it always progress and goes to new areas. Lets make a quick briefing what have made MS  for the past decade. I will go through big segments.

    1) Of course new versions of windows.

    2) DirectX, when it was born it was the underdog now it is the king of graphics in modern games.

    3) Xbox, era of play station and sega. I can say that if i play some game i would like to do it on a Xbox + kinect, atleast i would take off some kilos :)

    4) The enterprise sector. Here i will make a quick list of products: MS Sql Server(ok little more than 10 years) but as quality it is compared to oracle its really great server. More enterprise sharepoint servers, dynamics and alot more products.

    5).Net . How much this technology progressed, before time we were arguing with friends who were writing on java about c# vs java well now they dont argue, they simply say you won.

    6) Bing . I really think that with the new integration with mango and xbox live it will become my favorite search engines.

    7) WP 7 i really like my phone and wait for the mango update + i hope soon we start our WP 7 first application.

    i can continue to give great examples of technologies that really made a big point in the past decade. I write all this simply to show that microsoft goes to new areas all the time but think about this. Google is dropping projects but from all those things i mentioned MS havent dropped even one(except IE 6 :P ) .

    Html 5 is just a way to hit another market, it cant beat silverlight/wpf and the idea is not to fight with them. It is just a fact that all "developers" know html + javascript. Just bring bigger market and more tools for us.

    Friday, September 9, 2011 11:02 PM
  • I agree with you that WPF should not be compared with HTML5. It reminds me the first release of the Flash by Macromedia in 2001. I was consulting for a company as a MS Interdev developer and we suddenly faced with the strong marketing policy of Macromedia at that time to promote Flash as much as possible. It is true that Flash was/is great, but you cannot ever, never compare it with Microsoft programming languages. It might work well for the beginners, but will not work for senior developers who are usually working on enterprise level projects. With Flash, you have seen lots of fancy websites, but have you seen any multi-transactional applications such as online banking applications or monster e-commerce sites to use flash in their designs or in any of their developments?

    Using WPF in Visual Studio 2010 together with Microsoft expression Blend provides you capabilities that cannot be found in HTML5 at all. Microsoft will usually combine the best of each technology and will offer a package that long-term will show it works and performs much better. The Preview version of Blend is now available. You will notice that the performance has been improved a lot.

    For those of you in this forum that you have not heard about Blend Preview version, please read my recent post at:


    Amir Ahani, MCSD .NET + MBA

    Saturday, September 10, 2011 7:02 AM
  • Is it significant that there's been no mention of wpf5?

    Saturday, September 10, 2011 10:04 AM
  • I think that we will start talking about wpf 5 when when we hear something about framework 5.
    Saturday, September 10, 2011 10:14 AM
  • Yes, I am also waiting to hear about .NET 5.
    • Edited by Amir Ahani Sunday, September 18, 2011 9:38 AM
    Sunday, September 11, 2011 8:46 PM
  • Amir,

    Your post about Blend Preview is great. I actualy download the preview version and it seems to me that Microsoft has a strong strategy for Blend, WPF and etc. Do you have more resources about the new changes in Blend and WPF?



    Monday, September 12, 2011 4:52 PM
  • Well says , I am very concern about what technology shall I learn, I was about about learn properly WPF with C#.

    I already know a little bit of VB.NET. So one Question I want you to answer please, is that shall I go on WPF or start straight on HTML5

    Thursday, September 15, 2011 9:29 AM
  • Two different technologies two different purposes. WPF is mostly for desktop, html is for web. What kind of applications you have to develop. Generally WPF is more powerful and can achieve things better, faster and easier than standart web applications.
    Thursday, September 15, 2011 9:33 AM
  • Bryan,

    Please review my recent post about "WPF Useful Links" at


    Amir Ahani (MCSD.NET)


    • Edited by Amir Ahani Sunday, September 18, 2011 7:38 PM
    Sunday, September 18, 2011 9:40 AM
  • So now that the Build conference is over we now have a better picture of the future.  Looks to me that the most universal framework for all desktop/phone/notebook apps will be Javascript.  WPF is still supported as is C# stack (which is my favorite).  But just wondering... can Javscript be powerful enough for full LOB conerns?  I'm having a hard time with that and don't like Javascript.  But am considering just biting the bullet and getting on board with HTML5 and Javascript.  Also read that SL will integrate into WPF but that RIA will not be supported?  I understand where MSFT is heading but my head is spinning...


    Tuesday, September 20, 2011 2:43 PM
  • I dont think that the intent of Windows 8 and "Metro Style" is to replace LOB apps. I dont know if you can get the depth of PhotoShop or Excel in a touch application.

    As far as your comment about javascript being the most universal framework, i dont know that i agree 100% with that. Its true that if you know html/javascript you can now use that knowledge to build "Metro Style" apps but they are not web pages and they would not be usable on anything other than a Windows 8 box since they would use the new WindowsRT. I think that WPF/C# is just as viable of a platform to use for "Metro Style" as javascript since it uses the same WindowsRT, Microsoft just removed the language barrier. All web dev's can now build client side apps without having to learn a new language.

    HTML5 and JS will still be a key technology for web apps, but for Metro style apps, pick your poison.




    • Edited by sehlers Tuesday, September 20, 2011 3:05 PM
    Tuesday, September 20, 2011 3:04 PM
  • I wish Microsoft would give some guidance to the future of WPF, I didn't hear WPF mentioned mentioned even once at the BUILD conference, I was at plenty sessions but nobody ever mentioned WPF. However at the breakfast/lunch tables speculations was going on all the time, it is really hurtful to our business that Microsoft refuse to give a clear answer on the continued dedication to WPF.

    Dont get me wrong, I like Metro, but for LOB it is not useful, I dont see enterprises using Metro apps for normal office use.

    I like the performance of WinRT, but it is not possible to use in a desktop lob app, why not? Will it be possible in the future? Nobody at the conference would answer that question.

    My business has invested heavily in WPF and I have no idea what Microsofts vision for the future of WPF/desktop apps is.


    Thursday, September 22, 2011 9:12 AM
  • I believe Microsoft will continue their support for WPF. We can still write non metro style apps in Windows 8. You can view the below thread for details

    Since Microsoft wanted their users to adhere to new UI style (Metro Style), probably that is the reason why they might not have focused on their old technology which is mouse centric and Window based.

    I believe we can write LOB apps that adhere to Metro style design. I would say it is the matter of time for the users to switch to new UI paradigm.

    Ajosh Jose
    Thursday, September 22, 2011 11:24 AM
  • Jose,

    I dont think office workers in general will use a touch interface for LOB applications, things like data entry and apps with many functions does not lend themself well to Metro style designs. My customers have end-users with 3-4 monitors and many apps open at the same time, Windows 8 supports only one open Metro application on just screen (only exception is the split-screen functionality where you can have two apps open with one in a limited view), there is no support of multi monitors for Metro.

    Thursday, September 22, 2011 1:45 PM
  • I think it's the consumer product that is in the driver seat right now when it comes to programming technology, and for the moment, it is the future of Windows in tablet world and other mobile devices. If you consider that cheaper tablet PCs is outphasing laptop sales, it's imperative that Windows adapt to that circumtance. They are probably just considering the future where consumer will forgo buying a laptop(or even desktop PC) when tablet PC (including eReaders) has caught up with what most people use computer at home in the first place (hint, it's not opening Excel and Word document or firing up their company's ERP).

    I have not touch my desktop PC at home for 4 months now after my bank finally rolled out their mobile device app. I browse website and read news using a tablet.

    There is a business world dominated by desktop PC on the one hand, and an even bigger market for consumer products ruled by content services that is now the niche of mobile devices, on the other. The later needs a lean and efficient environment which WPF and Silverlight cannot provide.

    If Javascript seems like a roll back, it probably is. Microsoft has been developing product based on the assumption that hardware technology will eventually catch up. Now that they are faced with a very restrictive hardware of mobile devices (specially ARM processor) that development mantra is no longer suitable.

    • Edited by JRQ Thursday, October 13, 2011 3:59 PM
    Thursday, October 13, 2011 3:53 PM
  • Hi Everybody,

    I would like to share with you my notes about the recent presentation of Richard Campbell on Windows 8, and Build in BCIT:


    Amir Ahani (MCSD.NET) 

    • Edited by Amir Ahani Wednesday, October 26, 2011 11:17 AM
    Tuesday, October 18, 2011 1:24 AM
  • Hi Everybody,

    I would like to share with you my notes about the recent presentation of Rockford Lhotka on Windows 8 in Visual Studio Live! Redmond:


    Amir Ahani (MCSD.NET)


    • Edited by Amir Ahani Wednesday, October 26, 2011 11:17 AM
    Wednesday, October 26, 2011 11:17 AM
  • Directed to consumer . . . interesting . . . but without support for ARM processor I wonder if it will be a viable tablet OS.

    Does anyone know the footprint size of Windows 8?

    • Edited by JRQ Wednesday, October 26, 2011 6:25 PM
    Wednesday, October 26, 2011 6:17 PM
  • Just wondering what others are thinking now... Are you going to bone-up on Javascript and HTML 5 for Window OS apps?
    JP Cowboy Coders Unite!
    Friday, October 28, 2011 4:03 PM
  • I already know HTML and Javascript so perhaps that's a bias.

    I think the active tiles might be best using jquery but it;s just a guess at this point.

    I reckon there will eventually be another product like silverlight oob which'll be good for apps on winrt.

    Seeing as how the OS isn't anywhere near finalised, let alone tools.

    Difficult to judge what businesses would be using these theoretical arm based slates for.

    Monday, October 31, 2011 11:27 AM
  • What I see as the future for software developers is very clear:

    • Web developers can use HTML5, CSS3, and JavaScript skills to build native applications for Windows.

    • .NET Developers can use XAML, C#, F# and Visual Basic to build beautiful Metro style apps.

    • Game developers can use the power of DirectX 11.1 to build amazing, immersive gaming experiences.

    • Driver developers can use the new, integrated Microsoft® Visual Studio® development environment to increase productivity.

    To learn more please read my latest posts at:

    Amir Ahani (MCSD.NET)

    • Edited by Amir Ahani Saturday, November 12, 2011 6:54 AM
    Saturday, November 12, 2011 6:54 AM
  • Don't be so quick to jump the gun on dismissing Silverlight or WPF.

    Not all apps are going to be suitable for the new Metro side of Windows 8. There is still the traditional desktop, which will be essential for Business applications.

    As far as I am aware (Correct me if i'm wrong) there is no HTML5/Javascript support for non WinRT apps running on the traditional desktop.

    If you have Silverlight and/or WPF under your belt then to me it seems as though you are getting the best of both worlds.

    Some WinRT APIs will also be available to WPF/Silverlight apps running on the traditional desktop. I see them both as technologies worth having.

    Any of us who develop web applications using .NET Webforms or .NET MVC should by now have a good grasp on HTML/Javascript/CSS anyway, so I don't think people need to worry.

    Personally i'm happy with a number of technologies.

    The advantage of WinRT development comes (at first anyway) in my opinion when developing consumer applications that you want to sell through the Windows App Store, as you can also compile them to run on the ARM version of Windows 8 (Which supports the Metro style and not traditional desktop).

    The way I see it, it's more choices for developers. You use what works best for your situation.


    Friday, January 27, 2012 11:33 AM
  • I just thought of something here.  If developers choose HTML5/Javascript and interface to WINRT, will those applications be able to run on non-WINRT systems?  I mean if you call specific WINRT interfaces you won't be able to run those apps anywhere right?  If this is the case then isn't MSFT telling us that HTML5 will be the driving force on all API calls?  So it looks like, to me there will be at least two flavors of HTML5/Javascript programs 1) Non-WinRT specific API/Class calls and 2)Pure HTML5 (which will run anywhere).
    JP Cowboy Coders Unite!
    Friday, January 27, 2012 5:19 PM
  • Yes, ultimately there are specific WinRT calls that you will not be able to port over to a standard HTML5/Javascript website. This is the same for Xaml metro apps, you will not be able to use the same code and make a WPF app directly. I think the intent was to allow developers to use whatever language they are familiar with but there is still a learning curve with WinRT.
    Friday, January 27, 2012 5:26 PM
  • Very good thanks for confimation on that.  This means that the dividing line is this:

    If you want portable code, chose HTML5/Javascript only.  If you are a Javascript expert who doesn't know C# or VB.Net then you have to learn WINRT to write MSFT applications "Metro Style".  If you are a C# or VB.NET person and you want to use your skills on MSFT only platforms, then you have everything you need in WPF or System.Windows.Forms. 

    Interesting how Java introduced the write once, run anywhere model in 1990, and how we keep having to come back around to that concept.  If all platforms support Javscript, then hasn't it become the UNIVERSAL write once run anywhere language now that many companies have shut out Java?  Too bad we couldn't get C# to become the universal language, I think a ton of folks really like C#.  On the other hand, now that I'm learning Javscript, I'm finding that untyped languages are pretty cool... In fact they tend to support convention over classification.  As we dive deeper into typed languages we learn that convention IS very important.  So I'm just wondering how handicapped we've been over all these years sticking to strongly typed languages.

    If one looks into the "Favor aggregation over inheritance" principals and the Unity framework for Dependency Injection including Dependency Property getvalue and setvalue constructs, they're all done at the most fundamental OBJECT layer.  In javascript this has always been true, but unlike C#, no up and downcasting is needed to use the methods/detail.  So in a sense, Javascript allows us to not worry about what is contained.  Maybe Javascript has advantages...

    JP Cowboy Coders Unite!
    Friday, January 27, 2012 5:40 PM
  • Maybe.  But you have to also remember what this new model could do to the open source values.  Think of what Microsoft is doing with the Windows Store; I asked about this very thing a couple of months ago in another forum talking about publishing to the Store, and one of the moterators sort of pushed me away.  he didn't want to talk about Open Source in the store.  And not to mention, look what's up for .net; there is a .net 4.5 which is more like 5.0.  But my point here is that we could argue frameworks all night; they're all still supported.  The question is open source and whether that is supported in Windows8.  What will happen to the Outercurve foundation?  What will happen to all of the open source metro stuff they have put out?  If microsoft is really making us only have one place for metro apps in the name of our safety, if they really want to baby us that much, then what is the point of developing?  At least for enjoyment?  I'm not trying to diss propriotary software and people trying to make a living, but there are those who are more community driven and who love the open source model. 
    Saturday, June 9, 2012 7:04 PM
  • [...] JavaScript to me is the most arcane idiotic language on the planet today. [...]

    Maybe if you are used to statically typed languages it might seem bad, but it also gives you a huge ammount of expressive power. It's easy to misuse Javascript, way too easy, but also it's easy to use it right, all you have to do is think of prototypes and not classes, Javascript code is normally shorter than most of other languages alternatives, although it can get messy, if you know what you are doing you will eventually love it, don't hate it just because you don't understand it!
    Thursday, September 27, 2012 8:19 PM
  • Based on current tracks, not good. If you need jobs right away, WPF is good choice. I am having difficult time finding WPF developers. But Silverlight is dead. 

    Check out these two articles: 

    Are Windows Forms, WPF and ASP.NET Endanger?

    What is .NET Scope in Future

    Good luck!

    Sunday, January 27, 2013 4:55 AM
  • From what I've seen, businesses still rely heavily and will rely heavily in the future on strong client-side LOB applications written using frameworks like WPF. HTML5 just doesn't make financial sense for non-customer facing applications, and doubtfully ever will in my opinion due to the complexity required to make even a basic application.

    For customer-facing applications that are intended to have a broad reach, HTML5 and Silverlight seem to be the only popular options available. Silverlight won't run on mobile, but don't be fooled into thinking that that makes HTML5 a good will still run into the write-once, debug everywhere trap using a language and ecosystem that is nowhere near mature or performant enough for heavy lifting.

    For broad reach to standard consumers, writing native GUIs (apps) and relying on cloud services for backend services seems like the best way to do it now, IMO. Some customers, especially businesses like financial institutions, have issues with installing native software applications on PCs, and HTML5 may be the only option for targeting these companies.

    • Edited by Mikeg22 Sunday, January 27, 2013 3:53 PM
    Sunday, January 27, 2013 3:04 PM