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

Jerry Nixon

Jerry Nixon jerry_nixon Jerry Nixon

Niner since 2011

Jerry is a Microsoft Developer Evangelist in Colorado. 

See more entries…

Forum Thread Replies Latest activity
Coffeehouse Windows 8 Apps: Xaml vs. HTML5 31
  • UWP-021 - Implementing a Simple Hamburger Navigation Menu

    This section does a great job of demonstrating the Hamburger Menu. That being said, there are some styling issues that impact accessibility. These issues are resolved in this implementation: https://github.com/Windows-XAML/Template10/blob/master/Template10%20(Library)/Controls/HamburgerMenu.xaml

  • The Universal Windows Platform

    @HaraldHeide:I know you really mean JERRY.

  • Exam Prep Session for Exam 70-532: Developing Microsoft Azure Solutions

    At 6:00, I am 100% sure you mean "resilience" instead of resilence". But at the rate Azure is releasing new features, I would not surprised to see resilence showing up soon. Be a good name for a firewall service.

  • XAML

    At 6:10 Harini is telling us how to handle a specific "is this phone" UI. These are referred to as tailored experiences. The basic idea is that you don't; instead, you determine when you want to have a one-handed experience and to query the diagonal size of the physical device. This is not a visual state solution. This is a query on load and a separate XAML view.

  • Developer's Guide to Windows 10 Preview: (01) Getting Started

    @mumair85: Prism for Windows Apps has transitioned to open source/community. There is a plan to rev it, yes.

  • Developer's Guide to Windows 10 Preview: (05) SplitView Control

    Okay. I will publish this on my Blog so you can have the source. Give me a day or two. http://jerrynixon.com

  • The Future of WPF

    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.

  • The Future of WPF

    , 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.

  • The Future of WPF

    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.

  • The Future of WPF

    "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.

See more comments…