Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supporting Proxied/Wrapped ViewModels #629

Merged
merged 8 commits into from
Feb 12, 2016
Merged

Supporting Proxied/Wrapped ViewModels #629

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
48f8fd1
Added ResolveForPage(Page page...)
1iveowl Feb 7, 2016
cf1cab1
Add ResolveForPage to all three NavigateTo/From methods
1iveowl Feb 7, 2016
827945c
Update NavigationService.cs
1iveowl Feb 9, 2016
7e74bd1
Overloading ResolveForPage for backwards compatibility
1iveowl Feb 9, 2016
700765d
Update BootStrapper.cs
1iveowl Feb 9, 2016
e365da5
Update NavigationService.cs
1iveowl Feb 10, 2016
146dd0f
Marking ResolveForPage(Type) obsolete
1iveowl Feb 10, 2016
8611441
Remmoved exception when no ViewModel is resolved
1iveowl Feb 12, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Overloading ResolveForPage for backwards compatibility
  • Loading branch information
@1iveowl
1iveowl committed Feb 9, 2016
commit 7e74bd1a9cd2f62a6071db73b9be8c58aa08d3a4
5 changes: 2 additions & 3 deletions Template10 (Library)/Common/BootStrapper.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,10 +62,9 @@ public virtual T Resolve<T>(Type type)

/// <summary>
/// If a developer overrides this method, the developer can resolve DataContext or unwrap DataContext
/// available for the Page object if using a MVVM pattern that relies on a wrapped/porxy around ViewModels
/// available for the Page object when using a MVVM pattern that relies on a wrapped/porxy around ViewModels
/// </summary>
public virtual Services.NavigationService.INavigable ResolveForPage(Page page,
NavigationService navigationService)
public virtual Services.NavigationService.INavigable ResolveForPage(Page page, NavigationService navigationService)
{
return ResolveForPage(page.GetType(), navigationService);
}
Expand Down