patterns & practices: Prism for the Windows Runtime

Created Release: Quickstarts for Prism for Windows Runtime (May 20, 2013)

fcheung — Mon, 20 May 2013 18:31:02 GMT

The following Quickstarts are available for Prism for Windows Runtime:

EventAggregator Quickstart
Hello World Quickstart
Hello World with Container Quickstart
Validation Quickstart

Released: Quickstarts for Prism for Windows Runtime (May 20, 2013)

Mon, 20 May 2013 18:31:02 GMT

The following Quickstarts are available for Prism for Windows Runtime:

EventAggregator Quickstart
Hello World Quickstart
Hello World with Container Quickstart
Validation Quickstart

Updated Release: Final Release Prism for Windows Store apps (Apr 24, 2013)

fcheung — Mon, 20 May 2013 18:25:16 GMT

The final release is available at http://aka.ms/prism-winrt-code.

Released: Final Release Prism for Windows Store apps (Apr 24, 2013)

Mon, 20 May 2013 18:25:15 GMT

The final release is available at http://aka.ms/prism-winrt-code.

Source code checked in, #e3731fa995a46687362670fa1806572093a4c2ba

Francis Cheung — Mon, 20 May 2013 18:10:11 GMT

Moved AdventureWorks Shopper sln file to root and a few bug fixes.

New Post: Application Settings Navigation

shaggygi97 — Sun, 19 May 2013 22:14:07 GMT

Yes, I agree with you. It seems like you should ( in most cases ) be able to navigate deeper within the Settings for the user to enter/select info. However, if you have a larger amount of data to enter and validate... it would be more appropriate to navigate to the needed page.

I'm working on an app that may require the user to enter a number of fields and I was not sure what the best approach to this would be... Settings vs Page. If your team believes this is acceptable to navigate to another page, then I will continue to go that route.

Thanks

New Post: Prism for the Windows Runtime Book

shaggygi97 — Sun, 19 May 2013 22:06:44 GMT

Yes, I've started reading through this pdf. It would be nice to be able to purchase a hard copy similar to the Developer Guide to Microsoft Prism 4 from Amazon. It is nice to have a quick reference.

Thanks

New Post: Prism for the Windows Runtime Book

blainew — Sun, 19 May 2013 21:39:40 GMT

There is a pdf version at http://aka.ms/prism-winrt-pdf.

Is this what you are looking for or do you want a hard copy book that can be purchased?

blaine

New Post: Application Settings Navigation

blainew — Sun, 19 May 2013 21:37:47 GMT

The guidelines refer to flyout's instead of pages. Initially Add Shipping Address, Billing Address, and Payment Information were in flyouts which does not work well because the user will enter information that can be lost with light dismiss. The setting navigates to a page and pages can have buttons on them.

So the other question you are asking is since Add Shipping Address, Billing Address and Payment are pages should access to these pages be in the app bar instead of settings. Our interpretation is these are setting for the app and when we had our UI review, they did not disagree. We raised the issue about light dismiss being a problem and they suggested moving this information to pages. I will follow-up on your question to understand the preferred navigation for these pages. Given the discussion we had internally I think we are correct but I will double check.

Let me know if I'm understanding your question correctly. Thx.

blaine

New Post: Application Settings Navigation

shaggygi97 — Sun, 19 May 2013 19:20:46 GMT

The UI guideline shows the following for the Settings pane...

Inappropriate use of settings
•Don't add commands that are part of the common app workflow. These commands should be placed in the app bar or on the app canvas.
•Don't use an entry point to perform an action directly. Entry points should open a Flyout or the browser.
•Don't use the Settings pane for navigation. When the Settings pane closes, people should be in the same place in the app that they were when they entered settings. The app bar is a more appropriate place for navigation. For more info, see Defining layout, navigation, and commands.
•Don't use the SettingsFlyout class as a general-purpose control. It's intended only for settings Flyouts launched from entry points.

The 3rd bullet is what I was asking about. So in the AW demo, if you click Add ( shipping, billing or payment ) the app will navigate to the respective page. The bullet states the user should be in the same place in the app before and after using the Settings pane.

I can see the need to navigate to something if needed in some cases. However, it seems this example goes against the guidelines. Would it be more appropriate to have the Flyout navigate to a Flyout within the pane that included the address or payment controls instead of navigating the app?

Am I not understanding this correctly? Thanks

New Post: Application Settings Navigation

blainew — Sun, 19 May 2013 18:25:44 GMT

Shaggygi97,

Which flyout are you referring to? Do you mean Add shipping, billing, and payment information? If so those are pages.

blaine

New Post: Prism for the Windows Runtime Book

shaggygi97 — Sat, 18 May 2013 14:12:50 GMT

Great job on first release. It would be nice to see a book... even if it is the same material on website. http://msdn.microsoft.com/en-us/library/windows/apps/xx130643.aspx

Updated Release: Final Release Prism for Windows Store apps (Apr 24, 2013)

blainew — Sat, 18 May 2013 06:44:33 GMT

The final release is available at http://aka.ms/prism-winrt-code.

Released: Final Release Prism for Windows Store apps (Apr 24, 2013)

Sat, 18 May 2013 06:44:33 GMT

The final release is available at http://aka.ms/prism-winrt-code.

Updated Wiki: Home

blainew — Sat, 18 May 2013 06:38:33 GMT

The Prism library and the associated AdventureWorks Shopper RI demonstrate how to create Windows Store Apps using C# and XAML.

Just release Prism for Windows Runtime.

Announcement: Blaine Wastell's blog Post
Code: aka.ms/prism-winrt-code
Documentation: aka.ms/prism-winrt-doc

Overview

This project provides guidance to developers who want to create a Windows Store business app using C#, Extensible Application Markup Language (XAML), the Windows Runtime, and modern development practices. The guidance comes with source code for the Microsoft.Practices.Prism.StoreApps library, source code for the Microsoft.Practices.Prism.PubSubEvents library, the AdventureWorks product catalog and shopping cart reference implementation, and documentation. The guidance helps you implement MVVM with navigation and app life cycle management, validation, managed application data, implement controls, pages, touch, search, tiles, tile notifications, localization and accessibility. It also provides guidance on testing your app and tuning its performance.

Blogs and Twitter

New Post: Hadling Exceptions

maq_balrajs — Sat, 18 May 2013 04:07:22 GMT

Is there a centralized place to handle all exceptions that comes up in ViewModel or Model to be logged?

Created Unassigned: Assume Window.Current.Content inplements IFrameFacade instead of assuming it is a Frame [10]

dukeps — Wed, 15 May 2013 19:16:52 GMT

Classes like MvvmAppBase and FlyoutView should assume Window.Current.Content to be an IFrameFacade instead of an instance of Frame. This would allow for more extensibility for example, the scenario of building custom IFrameFacade.

New Post: Navigation Explanation

DCherubini — Tue, 14 May 2013 20:55:34 GMT

Hi,

Based on my understanding, the ListViewItemClickedToAction class defines an attached property that can be attached to a XAML control which can hold an Action<object> (e. i. a method that receives an object and returns nothing).

When attached to a ListViewBase, the ListViewItemClickedToAction subscribes to its ItemClick event. When a user clicks in the ListView, the ListViewItemClickedToAction is then notified of the interaction and executes the Action<object> that was set in the property (for example, the ProductNavigationAction) passing the ClickedItem as a parameter. In said action you can perform a navigation request using the NavigationService.

Regarding how the navigation process works, I believe you can find information about it in the draft documentation of the project:

Prism for Windows Runtime Draft Documentation

I hope this helps,

Damian Cherubini
http://blogs.southworks.net/dcherubini

New Post: What is the purpose to make private constructors of DelegateCommand that use Func executeMethod parameter?

AngkorWu — Tue, 14 May 2013 02:17:55 GMT

Thanks

New Post: ViewNodeId Errors

shaggygi97 — Mon, 13 May 2013 21:26:42 GMT

Thanks for reply. This is a weird one as my AW example does this too. Both apps show this error, but will compile and run. I also noticed the Back Button ( arrow ) image will go away in my design UI, but will show when running the app. If I close and reopen VS and the app, the error ( along with the swiggly blue line under the XAML in StandardStyles ) will go away. After a period of time it will begin again. I'm not sure how to reproduce, but will let you know if I see a pattern.

Thanks

patterns & practices: Prism for the Windows Runtime

Created Release: Quickstarts for Prism for Windows Runtime (May 20, 2013)

Released: Quickstarts for Prism for Windows Runtime (May 20, 2013)

Updated Release: Final Release Prism for Windows Store apps (Apr 24, 2013)

Released: Final Release Prism for Windows Store apps (Apr 24, 2013)

Source code checked in, #e3731fa995a46687362670fa1806572093a4c2ba

New Post: Application Settings Navigation

New Post: Prism for the Windows Runtime Book

New Post: Prism for the Windows Runtime Book

New Post: Application Settings Navigation

New Post: Application Settings Navigation

New Post: Application Settings Navigation

New Post: Prism for the Windows Runtime Book

Updated Release: Final Release Prism for Windows Store apps (Apr 24, 2013)

Released: Final Release Prism for Windows Store apps (Apr 24, 2013)

Updated Wiki: Home

Overview

Links

Blogs and Twitter

New Post: Hadling Exceptions

Created Unassigned: Assume Window.Current.Content inplements IFrameFacade instead of assuming it is a Frame [10]

New Post: Navigation Explanation

New Post: What is the purpose to make private constructors of DelegateCommand that use Func executeMethod parameter?

New Post: ViewNodeId Errors