@bc3tech - the new function bindings are for x:Bind, yes. However implicit boolean to Visibility is now supported in classic binding as well.
I work as a Program Manager on Windows client developer platforms, namely XAML. Prior to joining Microsoft, I worked for various customers doing application development in Microsoft technologies including Silverlight, WPF, ASP.NET and SharePoint. I mostly enjoy creating solutions for developers and listening to how customers use things I'm involved in so that I can continue to be an advocate for change within Microsoft.
|Coffeehouse||Free downloadable video material?||1||Sep 02, 2007 at 1:18PM|
|The 9 Guy Around The World||9Guy goes to Zend||0||Oct 24, 2005 at 11:13AM|
|Coffeehouse||Hello Tablet world!||383||Apr 14, 2005 at 5:12PM|
Apr 02, 2016 at 8:26AM
@lilepeeps:So rad...thanks for allowing me to be Belgian for the moment :)
@rtischer8277 the hub control is only the first level. You control the launching points from there. This is a pattern where the main navigation Starts from that hub experience of heterogeneous content.
@MikeKenyon -- Hi mike can you ask this question over on the forums (dev.windows.com)? I know it is annoying to ask, but I want others to have the answer as well.
UID support on primitives isn't supported, but this is something that I'll log a bug on to investigate.
Hi aL_ -- I think we must recognize that REST is a style, not a mandate. In the definition of REST as described by Fielding makes no such requirement that file extensions be hidden, but rather that the URI represent a state of an interface. The above still does wheter .aspx and # are present. The guidance for RESTful URIs is that a noun is used versus a verb so /SLTestAppPage/getView?view=HomePage would be lest noun-ish, but still represents and endpoint to a resource.
It's a semantic difference between a REST purist (hi-REST) and an interpretation I suppose .
But enough on that...viva Silverlight!
i also did a screencast about some of this a few weeks back -- "cheating" at creating a media player
actually, visual studio code snippets are much different in nature -- they are template snippets, rather than just blocks of code.
visual studio code snippets are templated by the author, providing intellisense integration into visual studio 2005...initiate a code snippet and then tab through all the settings to complete your implementation of that snippet.
they are living code snippets, versus just demo code/snippets.