caliburn-micro / caliburn-micro.github.io Goto Github PK

The second part of the WPF tutorial will cover this:

• How to add and use a menu
• How to add and use a dialog form, including using a WindowManager
• A link from the documentation index
• Created source code will be made available in the examples section of the Caliburn.Micro github

For now copy / paste documentation from codeplex across to the site.

Will review afterwards.

The old codeplex wiki pages should be cleared and only include a link to the new documentation on caliburnmicro.com to reduce confusion.

WeakValueDictionary is internal and therefore not available to implementors of IViewAware. Can we still safely use Dictionary <object, object> for view caching? If not, there is no migration path for projects that have implemented IViewAware

I posted the following question on Stack Overflow.

http://stackoverflow.com/questions/26702093/caliburn-micro-2-0-and-iviewaware-implementation-issue

Let us use this issue to discuss the detail for writing the migrating to 4.0.0 section.

I can see that there is all ready some work that has been started by Nigel I think we should expand upon that.

Migrating to 4.0.0

• ActionMessage.AssocicatedObject is not automatically set on win81/wpa81 (see Caliburn-Micro/Caliburn.Micro#24)
• FrameAdapter.CanCloseOnNavigating() on phone (Caliburn-Micro/Caliburn.Micro#17)
• design time support in WinRT (Caliburn-Micro/Caliburn.Micro#2)
• logging (Caliburn-Micro/Caliburn.Micro#14)
• conductors and activation/deactivation of child view models (Caliburn-Micro/Caliburn.Micro#1)

Guidance for those that are downloading via nuget expect a phonebootstrapperbase cause that is what is in the documentation. Probably need an adjustment to the docs to indicate the slight differences between WPA8.1 and WP8x (Silverlight).

https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages

but show up on https://caliburn-micro.github.io/atom.xml