Entries:
Comments:
Discussions:

Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

The Future of WPF

29 minutes, 36 seconds

Download

Right click “Save as…”

Jerry Nixon welcomes Unni Ravindranathan and Hari Menon from the Visual Studio Client Tools team as they discuss the recently announced changes, improvements and future of the WPF platform.  For more information click here 

  • VS_Download[1:59] Let’s recap some of the major  announcements that were made during the Visual Studio Connect event?
  • [3:29] How much did “User Voice” play into the decision process for what new capabilities are being rolled out?
  • [5:06]  What were the big announcements made for WPF?
  • [7:05]  Let’s talk about some of the cool new tools that are available to developers?
  • [10:20]  Why so many changes in Blend? What’s going on there?
  • [13:03] What is the Timeline tool?
  • [18:04] What about version support?
  • [21:02] Are there any changes to the XAML spec itself?
  • [21:56] Is there a plan for WPF to join Open Source or .Net foundation? 
  • [23:40] Any changes to the new toolbox?

 Follow the conversation @msdev
 Become a Fan @ facebook.com/MSFTDev
Subscribe to our podcast via iTunes, Windows Phone Marketplace or RSS

If you're interested in learning more about the products or solutions discussed in this episode, click on any of the below links for free, in-depth information:

Websites & Blogs:

Tags:

Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
    Unsubscribing
    Subscribing
  • Jerry Nixonjerry_nixon Jerry Nixon

    And I quote, "If you are going to start an application today and it's going to be a line of business, desktop application, it's going to be native and you want that fidelity, our premium UI framework is WPF." That's right.

  • MaxMax

    I would like to hear something about silverlight, anything. Is there even a silverlight team in microsoft? If not, please, make clear statement on the matter.

  • @Max: Silverlight is dead. It's life was stretched out a little with Windows Phone (though that's a Silverlight of a different color), but even there they've moved on. Don't expect any news about Silverlight.

  • Will you fix the support for loading Xaml Resources from inside the InitializeComponent?

     

    https://alexfeinberg.wordpress.com/2014/11/08/microsoft-mechanism-to-load-wpf-resources-is-broken-looking-for-a-better-title/

  • Jerry Nixonjerry_nixon Jerry Nixon

    @Max: There are no plans to further invest in Silverlight. This is far less of a technical decision as it is an economic one. Many things have already been said officially about Silverlight from Microsoft, including our commitment to support it through our normal support policy.

    That being said, nobody is talking about Silverlight because the overall strategy of our whole industry is moving away from browser add-ins. Starting a Silverlight project today would not be fool-hearty, but it would certainly not be future-focused. The same could be said about creating a Adobe Flash-based application for your enterprise. That may never have been a great idea, but today it would be a silly one. Microsoft line-of-business technology is WPF. WPF is getting the investment. If you want to develop for mobile, then develop on XAML for Windows Runtime.

    The problem with replying to your comment, is that I can't reply with what you clearly WANT me to say. I wish the messaging had been more clear because you are not alone in your confusion or missing the messaging altogether. But Microsoft's XAML investment is WPF and WinRT. Is that the right decision? Is that the best decision? Does everything make sense? It doesn't matter. It is what it is.

    I hope that gives you at least a little of what you wanted - and may have already known.

  • Its great to hear something from Microsoft about WPF instead of the last 3 years which have been dominated by WinRT and Metro apps. Nice to have improvements in performance, visual studio integration and debugging. How about changes to the WPF controls - is there many fixes or updates being made? For example an improved DataGrid would be useful ... its pretty difficult to work with as is.

  • Vladislav Borovikovvborovikov makes software since 1849

    WPF is heavily tied to Windows but there are some good parts that can be ported. Are there any plans to make a portable core with XAML and data binding services?

  • zerkzerk

    "a line of business, desktop application"

    1. MS doesn't want that new application to be a Universal App? Even under Windows 10? Why not? Is it cut off from using the hardware, or is it just the need for legacy Win 7 and old device support?

    2. How many LOB, desktop apps is MS imagining there will be in the future? Specialty things like CAD, Photoshop, etc. But already a huge number of LOB applications are browser based. Is there some guidance about the future of such applications?

  • Dmitry Lyalin (Microsoft)LyalinDotCom Product Manger for Visual Studio

    Great video :)

  • JonJon

    So in other words, no real improvement to WPF. No new controls, you get to pay for third party ones. No real new activity. Wow, they fixed up Blend a little. All the resources are going to the Win 8 train wreck of a UI I guess.

  • Glad to know there is still a significant development effort on WPF.

    And always good to see the guys behind all this stuff. :)

    This is directly going in my optimistic elements about WPF future: Is WPF dead: the present and future of WPF

  • Jerry Nixonjerry_nixon Jerry Nixon

    "a line of business, desktop application"

    1. MS doesn't want that new application to be a Universal App? Even under Windows 10? Why not? Is it cut off from using the hardware, or is it just the need for legacy Win 7 and old device support?

    2. How many LOB, desktop apps is MS imagining there will be in the future? Specialty things like CAD, Photoshop, etc. But already a huge number of LOB applications are browser based. Is there some guidance about the future of such applications?

    @zerk: the WPF app is the "universal app" (so to speak) when we talk about spanning versions of Windows. Only a line-of-business app written in Windows Presentation Foundation can be enjoyed by both Windows 10 users, Windows 8 users, and Windows 7 users. (To be fair, native, WinForms, and Web can also deliver this value).

    Typically, enterprises can't handle or afford upgrading every user on the network. That makes WPF a great choice for large enterprises trying to understand what they can do to keep their business going while they roll their upgrades over a few years.

    But are they compromising with WPF? Not at all, because Windows Presentation Foundation is still the godfather of XAML - with the most features and most coverage of what Windows can deliver for users.

    But even if your enterprise was 100% Windows 10 already (nobody is, by the way, it's still in preview) WPF still has a million great reasons to choose it - not just developer skills, either; sometimes you need to talk directly to the system, directly to the drivers, directly to the services, directly to the database - whatever your reason, whatever your specific business model, WPF lands as the choice again and again.

    As we see the evolution and expansion of WinRT-XAML we'll start to see those choices go either way. But, in today's world, where Windows 7 is still a common OS in the enterprise, WPF is the "universal app" for line-of-business solutions that spans all the versions of Windows. Eventually, developers will want to choose WinRT-XAML because it will be the super-set of all XAML and they can reliably know every desktop in their enterprise is Windows 8+. Until then, WPF.

    Your second question about how many line of business apps there are. If you think CAD or Photoshop are line-of-business apps, then you aren't really in this conversation. Every large enterprise has one to several custom line-of-business applications written specifically for their business, specifically to given them some type of marketplace advantage or some type of industry differentiation.

    Sometimes these apps are there for regulatory reasons or efficiency reasons or even business intelligence visibility. Lots of reasons - and today there are thousands and thousands which are responsible for billions and billions of dollars and millions and millions of widgets.

    Line-of-business applications are typically internal, secret, and proprietary. You may not see many, you may not think they are many, but there are tons of them - and they are mission critical; in some cases they are the intellectual property that valuates a company. So, when we talk about how important WPF is - in a way, we're talking on a global, economic scale.

    I hope that makes sense. Good questions.

  • Jerry Nixonjerry_nixon Jerry Nixon

    So in other words, no real improvement to WPF. No new controls, you get to pay for third party ones. No real new activity. Wow, they fixed up Blend a little. All the resources are going to the Win 8 train wreck of a UI I guess.

    Nope, I think you missed it. You can cynically gloss-over the hard work going in to enhance WPF. You can pessimistically disregard how in the scope of past WPF updates this one is one of the more significant. You can do a lot, @Jon, but you would be very inaccurate.

    This is the next version of WPF, the response to user voice/connect requests, significant performance improvements, instrumentation of the framework, and the introduction of new tooling that developers have been requesting for years. You may not see whatever you were looking for in this list, but your conclusion that there's nothing to it doesn't reflect reality.

  • Thanks for the your answers Jerry, especially clarifying the term "Line of Business" Desktop Application.

    I'm still working with C++ and a legacy GUI System. Some month ago I privatly started to really explore the .NET Framwork and the possibilities of WPF.

    I hope my question will not be totally off topic, but onee question that arises - and thats a Major decision point in our company:
    Does it make sense to develop a Desktop Application bind to the Windows OS or do you write your product as a HTML5 application?
    I'm don't really into HTML5, but I've a personal feeling, that the more complex an application gets the more it would be a pain and the more error prone it would be to do the job in HTML5. Are there anywhere unbiased articles or Blogs where you sum up some criteria and get a recommenadtion if you should use WPF or HTML5.
    And also if you maybe want to run a part of your application on mobile devices - ist there some support where you can reuse part of your model or even the XAML concepts for a native GUI ( maybe XAMARIN)?

     

    p.s. Saw you first on the Microsoft Virtual Academy C# Jump Start with Daren May and you guys where hilarious.

     

  • Jerry Nixonjerry_nixon Jerry Nixon

    , Charles​Duchemin wrote

    Does it make sense to develop a Desktop Application bind to the Windows OS or do you write your product as a HTML5 application?

    Charles, I love this question - choosing between .Net and HTML. Of course, I realize you really mean JavaScript, not HTML. XAML is the nearest corollary to HTML. But when you are building a solution, you're really weighing JavaScript and .Net (probably C#).

    This discussion is far too elaborate to give it any real justice here in the comments (like that will stop me), but when we try to replace C# with JavaScript, we are trying put an interpreted, scripting language into the shoes of a compiled, managed language. I don't think it's fair.

    The clincher to me is, when I picture a 100,000 line application written in C# - I don't even think twice. We have the tooling to manage that type of code. But 100,000 lines of JavaScript? Kill me now! And 100,000 lines is NOTHING in a line-of-business application. 1,000,000 lines is common - especially when we introduce the joy of code generation and unit tests.

    Think about things like Code Analyses, Memory Profiling, live XAML Tree, Code Coverage, Timeline and Power profiling, rock-solid third party controls, trusted enterprise design patterns with .Net - there's so much to love. So many reasons to lean toward it.

    But web applications can blur the lines. You can have .Net on the server and JavaScript on the client. That certainly works. Thousands of web sites have proven it. But what's best for your company? Hmm. Do you want the integrated security and fidelity of a native application on the desktops of your enterprise? Or do you want what is ultimately a compromise to what HTML/JS can do in whatever browser your IT department allows installed?

    It's not an simple answer. Sometimes a web-based application is quicker to write and easier to deploy. But most line-of-business applications are not quick and easy. They take a team of developers months or years to write. They are secure, transactional, scalable, and significant. If I were writing the checks, I would commission many web-based apps. But the one that runs my business, the one where I bet the farm? I'd likely prefer solid, proven technologies like .Net - where thousands of Fortune 5,000 companies have led before me with proven success.

    Just like you can use Notepad instead of Visual Studio, I believe you could make a JavaScript solution work. I really do. But when it comes to cost, scale, and maintenance - I don't think the argument for large-scale JS is valid. And insofar as user experience from the fidelity on the client, there's no comparison. Enterprise, line-of-business developers love WPF for a reason - it delivers an elegant solution without compromise. 

    But, in the end, only you know your company and its variables.

  • OndrejOndrej

    The Future of WPF: Terrible designer, chaotic XAML causing three times more coding than in Windows Forms, inexhaustible number of bugs, lot of them silently swept under the carpet.

  • PierrePierre

    WinRT - the OS/2 of 2014.

  • Jaime abulaJaime abula

    Silverligth may be the main reason why so many developers stayed away from the windows store. The people that say that silverlight is dead, I think they don't start to understand the mess that the demise of silvelight caused. With the open sourcing of .Net, MSFT is doing the same thing that it had with silverlight. Except that silverlight was far, far more complete.

    Just turn the the plugin into a runtime... Problem fixed

  • In my opinion WPF/XAML is not an option anymore, even if they are trying to give a new boost with Xamarin, the reason you can create complex Line-of-business apps with HTML5 /Javascript nowadays you have a lot of frameworks that help you to create them.

    And If you decide to create mobile apps,Apache Cordova is a better choice instead of Xamarin because if you compare costs, development time, code reusability and learning curve, Xamarin has higher costs,higher development time and higher learning curve than Cordova, and on the field of code reusability you got 65%-70% with Xamarin and 90% on Cordova meaning that you need to rewrite on Xamarin at least 2 times some functions in order to work on ios/android.

    Add to the equation the phrase "Cloud First, Mobile First", and it is easier to work with HTML/Javascript the JSON outputs of a Cloud api.

  • yetiyeti

    "The Future of WPF: Terrible designer, chaotic XAML causing three times more coding than in Windows Forms, inexhaustible number of bugs, lot of them silently swept under the carpet."

    I think you're just lame programmer. More than 90% of all devs are. Just complaining and begging Resharper can write your code itself.

  • "The Future of WPF: Terrible designer, chaotic XAML causing three times more coding than in Windows Forms, inexhaustible number of bugs, lot of them silently swept under the carpet."

    I second this!!!

     

  • So how do desktop apps fit into the cloud monthly revenue stream?  They don't.  So while MS pays lip service to the current WPF users the goal is to get everyone, and I mean everyone, paying a monthly fee.  It's not about what technology is best for the customer, it's about the monthly revenue stream.  The idea that you can write a LOB WinForm application and use it for ten years scares the hell out of MS.

  • mikemike

    It's all about monthly fee now. People.

  • MichelMichel

    Montly fee and WPF??? Explain because I simply do not get it. WPF has no relation to cloud service per se. You can compare WPF to WinForms except that WPF gives you a lot more control over the UI experience and it gives you a good platform for MVVM design.

  • mhomho

    Could you please say something about the question from "vborovikov":

    WPF is heavily tied to Windows but there are some good parts that can be ported. Are there any plans to make a portable core with XAML and data binding services?

  • Aleph0mcAleph0mc

    WPF: a failure, much better WinForms. This technology should be revised and changed completely.

  • DanDan

    Anybody saying that WPF & XAML is crap and WinForms is better didn't get it.

    Make yourself a favor and take some time to learn XAML, its much more powerful, flexible and beautiful than WinForms.

  • DennisDennis

    With Siverlight pronounced dead, is there a way to use XAML/WPF/.Net in the web environment? Is it ASP.Net? Is our only option JavaScript/HTML?

  • JohnJohn

    RE: Discussion of toolbox starting at 23:40

    The lack of Microsoft investment in WPF controls is very disappointing. Yeah, there are some very nice third-party controls. Guess what? They cost money! Often a lot of money! Not a problem for corporate LOB app development, but a barrier to anybody else using WPF. MSFT has billions in the bank -- go buy Infragistics. :-)

  • @Dennis:You should give a try to HTML5/JS, you would find it easier and more powerful than silverlight and of course your apps will run on any mobile device

  • DennisDennis

    I have looked at HTML5/JS. It actually appears to be more difficult to master because there are so many frameworks and IDEs to choose from. It certainly seems more difficult and confusing to debug. And your code ultimately depends on the browser implementation of JS and HTML.

    The plugin approach was promising in that the browser inconsistencies could be minimized. If it wasn't for Apple and Google killing plugin support Silverlight and Flash would still be flourishing. It will be interesting to see if they come back as Microsoft's tablet market share grows.

    Anyhow, I'd still like to know if there is a way to utilize XAML, WPF, and the .Net framework in the web development environment without the dependence on Silverlight.

  • Mark LibnerMark Libner

    Great video guys! I can't wait to use these new tools. Keep up the good work. Thanks for taking the time to tell us what's going on with WPF. Us LOB developers down in the trenches could always use it. :)

  • DeonDeon

    Still unanswered: Most LOB applications have to be deployed online. That's where Silverlight excelled - XAML + Online deployment. How are WPF LOB apps to be deployed in future? I personally don't care whether there's a C# to TypeScript/JavaScript conversion system built into WPF, but WPF should be able to deploy to browsers!

  • Ton HisTon His

    Strange that Microsoft say to abandon Silverlight without given a viable alternative, just by saying that using plugin is not the way to go. There is no alternative at this moment to develop Web application, especially LOB, with ONE technology that has a rich UI experience like “traditional” winform applications. ASP.NET still rely on javascript and css. The same for HTML5/JS/CSS combo and as mentioned by others, both asp.net and html5 combo still rely on browser support, especially in rendering controls. Microsoft should NOT introduce new technology and abandon it within a few years like Silverlight where a large developer community has invest in Silverlight. Look at http://dotnet.uservoice.com/forums/4325-silverlight-feature-suggestions where developers still asking for new features. Why not integrate the Silverlight runtime in the .net runtime i.e. by transforming xaml to html etc.? Developers need ONE technology to develop applications for multiple devices independent of the chosen browser rendering engine….

  • @Deon:Check out the clickonce deployment feature in Visual Sudio.

  • DeonDeon

    @mjhillmann: Why you should NOT use Clickonce deployment
    http://www.codeproject.com/Tips/370532/Why-you-should-not-use-Clickonce-deployment-as-you
    In addition: Some companies (such as mine) do NOT share networks across business units.

  • WPFdevWPFdev

    what a great video jerry, very informative, unni and ari where excellent,if you could have been a tiny bit less fanboyish, and stayed on topic more it , but I have to say very nice job @jerry, and your advocacy of WPF in the comments is was some of the better stuff I’ve seen, just a couple point and this is hope you take constructively and keep in mind Im just a humble WPF dev and you are a Rockstar (I mean it, this video has 186k view in less than a month,OMFG, more popular than any keynote or anything else I could think of to search for on channel 9, maybe you should be a primary program manager) so with all due respect I would point out, since I have had first-hand experience with the .net code that was release on Github has been very over hype and the your statement that “now .net is on Mac and linux” was very misleading, only .cs files where released, no way to build anything, anyone can see for themselves by downloading it and try to get even fairly simple modules to resolve their external references. In theory it could run anywhere, the mix marketing messages at connect made it appeared to make a ”Connection™” to Xamarin but the fact is just for entertainment purpose as of now. the real deal is WPF is already cross platform, It looks awesome on Windows 10, I’m running it on 7inch tablet and yoga 2 pro 3200x1800 13inch, the one thing that’s obvious WPFs ability to customize every detail of your UI, including the size of slider and shape of thing like slider handles set it apart from every other platform.
    So when you say “If you want to develop for mobile, then develop on XAML for Windows Runtime”
    I say I have mobile WPF in my hands today, the writings on the wall to push Windows mobile 10 as Windows 10 mobile, no one will fooled, artificially trying to make RT the only option is doomed.

    “As we see the evolution and expansion of WinRT-XAML we'll start to see those choices go either way”
    I can’t figure out what that statement means if you’re trying to give encouragement to WinRT-XAML crowd your not doing them any favors and all the talk about future-focused development is meaningless, it’s really fear focused, and giving them the hope that MS can still provide a protected platform for them on mobile is not a good idea, don’t you know where a lot of the insane anti-MS folks get started, it’s a dog eat dog world and RT is wearing bacon underwear, the tablet of the year the beautiful Samsung galaxy 5, intel base android.
    Tell them how you’re going to stop Chinese manufactures from making real x86 windows 10 phone when they see what WPF can do on mobile. Go ahead and do another phone face plant, while the world leader in semi-conductors releases its next generation of mobile CPU, WPF will be here when you’re ready to grow up cheers!

  • Jerry Nixonjerry_nixon Jerry Nixon

    What a great video Jerry, very informative, Unni and Ari where excellent.

    <snip />

    WPF will be here when you’re ready to grow up.

    Hey, that video was fun to make and there will be more coming. First, thanks for wording it like I still have some growing up to do. I like to agree. And we're also in agreement with the future viability of WPF.

    That being said, the level of investment around WinRT-XAML is nothing to be ignored. Because it is important to Windows itself, WinRT-XAML will continue to evolve into a powerful successor of WPF over time. That is to say, Windows has traditionally employed several UI technologies but is now consolidating on XAML - not for apps but for the OS.

    This makes WinRT-XAML the beneficiary of performance tuning and other capabilities that will eventually make it an equal or maybe better option for the WPF line of business developer. Windowing, Win32 access, cross -architecture, cross-platform, inking, touch, NUI, and more. As the modality of computers evolves, WinRT-XAML will be compelling. To cutting edge apps, this is already true. To others, it may take time for this transition. For some, it may never happen.

    I'm certainly not disagreeing with your premise. It sounds like we are both WPF fans. But I do think there's a freight train around WinRT-XAML coming that shouldn't be ignored by developers. Thanks for your comments. Thanks for using the platform. Thanks for your contribution.

  • WPFDevWPFDev

    should have read
    "WPF will be here when they're ready to grow up",
    This being my first impression you, you seem plenty mature @jerry,
    I think your enthusiasm helped unni and harri share a lot of helpful insights,
    It was great to see the vison and focus they have.
    What was referencing to WinRT people. I think all WPF devs realize
    Level of investment in RT, emotional an otherwise. But I also think anyone who has mastered WPF would feel like that could take on a billion RT dev. single handed, maybe one hand behind the back.
    Look at the number of tick tack toe and tip calcs, don’t tell me about the
    HULU or some chezzy kids game.
    I have been doing a lot of interop lately, even with the RT resources,
    I’m not going into details, but do you think it’s really that big deal to say
    Thru a WCF service to get anything to negotiate airspace with anything including DirectX,openGL,sharpDX,C++ Native or anything else, it’s like the guys were telling you about all the mission critical WPF that aren’t generally know, except it’s way bigger than that, there are way better
    Practices for using WPF in almost any area you want to talk about. For example @alfien question.
    “Will you fix the support for loading Xaml Resources from inside the InitializeComponent?”
    Application.Current.Resources.MergedDictionaries.Clear();

    DesignerWindow.Resources.MergedDictionaries.Clear();



    Application.Current.Resources.MergedDictionaries.Add(
    Application.LoadComponent(
    new Uri("alfeinGreatCustomResource.xaml",
    UriKind.Relative)) as ResourceDictionary);

    Can be run anytime you want, put a window_loaded if you want to set styles on startup. Just because you can’t find every solution for your WPF with google search, might not mean what you think it does, if you think RT has any advantage(no one saying you didn’t try) , maybe your reality isn’t as real as is seems. The things you don’t know about WPF would shock you,the the graphic rendering alone requires massive polyfill on every other platform in existence, I know this for a fact, first hand, I don’t think people are sick of graphics, I can why many people would probably get the impression that Microsoft thins so from the solid color boxes, text, and images that is, you know. It’s really of no consequence what becomes of RT to me, I’m just saying, it’s over save the yelling and mashing of teeth, just sayin, no offence.really.

    An to all the RT devs out there , don’t worry you can really reuse your XAML skills this time!
    Come on in boys, the water is fine!

  • WPFDevWPFDev

    I wanted to try and get my mind around the magnitude of what 180k in view in 30 days , so I googled Blake Sheldon’s new hit “Neon Light” (at the end of the tunnel), in a catch ditty, it stays in D Flat the whole song, which is really tricky for the vocalist as well as the musicians, they have use syncopation and continually change the cadence of melody to maintain the listener interest. I don’t care what dictionary you guys are using but cadence and tempo are not the same thing, melodies have a cadence (there are even rules of cadence for melodies), people in every language speak with a cadence, matching bands march to the cadence on the percussion section, unless they are doing bang,bang,bang to a steady beat, or someone speaking monosyllabically at a steady pace, drives me crazy when you say it wrong, reminds me of Biff in back to the future. That said I was shock to see around 802k since Sep 12 (esp when it’s the first thing that comes up as soon as you type “blake s” into google), you may not have heard of Blake,(I understand most RT devs watch Big Bang Theory exclusively), he has a pretty good single show on NBC, they had there finale last night, I’m pretty sure it’s the highest rated show on NBC(its #1 US TV Network(Channel), just to be clear), so WOW!

    “But I do think there's a freight train around WinRT-XAML coming that shouldn't be ignored by developers”
    I think “train” analogy is spot on, you have the “WinRT-XAML train”, the “WP-XAML train”, the “Xbone (uni app?)Train” and the “Asp.Net.Vnext”, all on the .Net core (One core?, U2s sing for free these days ) track, and there no doubt they are redlining(Scum style, minus the responsibility part) . wooooo,woooooooooo, “they think they can”, “they think they can”, “they think they can”
    “They say they can?” woooooooooooooooooooooooooooooooot, now someone find MCfly and that hover board ASAP, were approaching 88 mph! , we gotta get back to the “Future”(inronically cra cra fav word) Part 3.

    I just feel bad for those who think is another light at the end of the tunnel, I like Blakes take on light at end of tunnels, is about how I feel about the promotional fear driven, attempt at driving developer demand was/is deeply flawed. WPF case in point!

  • WPFdevWPFdev

    I got that number wrong I just double checked its 2.4M or ove 10x more than you over 3 months, so your less only 1/4 as popular , aka , "a nobody", just gland I was able to correct before your head started swelling, opps!,

  • Please avoid revolving chairs on the show! I got dizzy!

  • WPFDevWPFDev

    That’s kind of what I thought you would say @Jerry, I suggest someone make a close inspection of that .Net core flux capacitor, you don’t want to have the world largest Wyle Coyote moment. Is that a real flux capacitor, or just some neon lights and rubber bands in a funnel? And is 1.21 jigawatts going to be enough energy? Are watts even an amount of energy? Or is it more like mph or tempo, it’s so frustrating trying to make sense of things when people say it wrong, it’s about as useless as a screen door on a battleship.

  • rOBrOB

    Great video, but Jeremy was so enthusiastic it kind of distracted from it. I kept thinking this is like an over-excited developer meeting his heroes while under the influence of MDMA.

  • MrThereMrThere

    Sorry to report that I have no faith in Microsoft. I switched to iOS and I'm making more money now. Good luck all you WPF developers

  • @LyalinDotCom: Great to hear you mention performance at the top of your list. Sadly it doesn't sound like MSFT are acknowledging the architectural performance bottlenecks which are widely known by the community that make it almost impossible to get 60 FPS (or even 30FPS) in all by the simplest of visual trees.

    Is the performance tool going to get down to the level of DUCE ("Dynamic Unified Composition Engine") and below so we can see the inefficiencies of primitive rendering? It will be good to be able to show MSFT what inefficient use of even the most basic GPU is made by WPF.

  • Robert AgansRobert Agans

    Hi Jerry,
    I wasn’t able to watch the film, but I read all the comments at the end of your blog, The Future of WPF, and was very glad to read what you had to say about WPF – it’s perhaps my favorite platform. Also your comparison of JavaScript with C#, although I use Visual Basic exclusively. I’m 78 years old and my vocation is my website at www.bobagans.org, and my hobby is computer programming. What I’m looking for is some exceptional WPF or MVC examples to give me some ideas for new future personal app’s to build for the pure pleasure of it.

    I’ve been using various Microsoft platforms, and others, for the past several years to develop a number of app’s, some that I use regularly and some just for the enjoyment of putting them together. These were all done on a desktop, and I now have an HP with Windows 7 Pro and a 22" TV monitor. I also have a 17" HP laptop with Windows 8.1 on it.

    The platforms that I like and use on my desktop are Visual Basic, WPF, MVC and Linq to SQL which I prefer to EF. I have tried a Windows store app on my laptop using VB and JavaScript, but I don’t like JavaScript and so have lost interest in it; in fact, I don’t care for the whole mobile-cloud scene that everyone seems so excited about.

    I would appreciate knowing where to find these exceptional examples, thanks, Bob.

Remove this comment

Remove this thread

Close

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.