I think I was misunderstood. I meant .NET Native. We want it for ASP.NET! 
Ahhhh … Yes. Essentially this is a factor for C#. So if you are using C# for your ASP.NET server side code then yes.
Really handy video, @RockyH. It’s very hard to understand how all this fits together, so a basic overview like that is really valuable. 
Thanks @ralphm I’m writing a book to cover building apps and services this way. It goes in to just a bit more detail than the video. 
I truly believe that the DiD approach is the future of app development.
2 Likes
IMHO it’s already here now and has been for a while
1 Like
I think the idea of Device Independent Delivery has been, but in my experience, few people are doing it correctly or efficiently. Too many organisations do multi-team siloed development and get zero code reuse. Or they do a really half-… job on all but one of the platforms they chose.
Since Java “write once, run anywhere”
Java innefficient? Half-adf.ly? meh, debatable I guess.
I can’t help but think that keeping up with all the current platforms would be a massive undertaking let alone what’s on the way, seeing as the diversity is growing logarithmically and not linear. But from what I’ve learned in these sessions recently I’m sure I’ll be spending some time and effort digging deeper and getting my hands dirty.
For XAML visual design Microsoft made a great IDE called Expression Blend. You can also design a lot of elements in Expression and export them as a XAML resource dictionary.
1 Like
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.