Advanced Forum Search Results
-
David Poll, PM on the Navigation feature for SL3, has posted some blog posts that may help with Prism + Navigation working together.
His blog : http://www.davidpoll.com
His navigation-related posts : http://www.davidpoll.com/tag/navigation/
In particular, this ...
-
This doesn't sound like something Navigation is going to be much help on. Could you consider having the Address "Page" as a UserControl instead and use its Loaded event to determine when to run your initialization logic?
Navigation is really just about a Frame that hosts Page controls - one at a time. It will only call ...
-
To answer your original questions questions:
Q1) You need to target the Hyperlink to a Frame so the Hyperlink knows which Frame it is going to navigate - you can do this by setting the TargetName property on the Hyperlink. So for example, in your code above you could set TargetName="f1" to navigate the Frame with ...
-
[quote user="MisinformedDNA"]
[quote user="AustinLamb"]
It depends on how you're mapping "Customers/X". From the way you're describing it, it sounds like you're doing something like this:<uriMapper:UriMapping Uri="Customers/{customerID}" ...
-
Ah, if you're not aware, there is an even lower hook point you can use that may avoid you having to take a dependency on System.Windows.Controls.Navigation.dll (and save ~26K in your XAP). It's Application.Current.Host.NavigationState (and the NavigationStateChanged event). This is the deep-linking hook into the browser that ...
-
The post you refer to appears to be dealing with the SL3 Beta - and we did have a bug where binding to Source didn't work correctly.
Can you perhaps share your project with me ( austin.lamb@microsoft.com ) and I can try to understand what's wrong?
Note that I'm about to get married so will be on vacation for 2.5 weeks, so my response ...
-
CanGoBack isn't quite that - it is whether or not the given Frame (or its corresponding NavigationService) can go back - which is not an application-level question. So you may have 3 Frames, one of them has CanGoBack=true, two of them have CanGoBack=false, if you'd only ever navigated the first one. Making this also respect ...
-
Maybe I'm misunderstanding your question somehow - Silverlight's Navigation framework has nothing to do with calling services. You're referring to two distinct concepts.
1) Navigation - how the user gets around the application. This is what the Navigation framework in the SL3 SDK addresses, and what my post above is ...
-
It was renamed to ValidationSummary in the final release of Silverlight 3. It's in the SL3 SDK, in System.Windows.Controls.Data.Input.dll, in the System.Windows.Controls namespace.
-
One option would be to use a HyperlinkButton, and set the TargetName to the name of the outer Frame. This should walk up the tree until it finds the correctly-named Frame.
Or, you could do what it's doing yourself - just walk up the visual tree (using VisualTreeHelper) until you find the outer Frame and call methods on that.