Intersoft Community - ClientUI - NavigationEventArgs : no ExtraData in WPF?

NavigationEventArgs : no ExtraData in WPF?

Alastair — Fri, 27 May 2011 02:33:07 GMT

Works like a dream Riendy - many thanks for this and the quick turnaround.

All the best,

Alastair

NavigationEventArgs : no ExtraData in WPF?

Riendy — Sun, 22 May 2011 22:12:28 GMT

Hello Alastair,

I've already sent the release nightly build to you.

Please do not hesitate to ask us if you still have any question.

Regards,

Riendy Setiadi

NavigationEventArgs : no ExtraData in WPF?

Alastair — Sat, 21 May 2011 08:00:34 GMT

Thanks Riendy, have emailed you the address.

Appreciate the efforts here folks, thanks.

NavigationEventArgs : no ExtraData in WPF?

Riendy — Thu, 19 May 2011 04:31:45 GMT

Hello Alastair,

Our development team has fixed your issue, and now I want to send the release nightly build to you. Could you please let me know what is your email address?

Riendy

NavigationEventArgs : no ExtraData in WPF?

jimmyps — Wed, 18 May 2011 07:42:00 GMT

Hi Alastair,

The released 13th build doesn't seem to include the check-in for this particular fix. It was the dev internal nightly build that I referred.

Our support team will send you the release nightly build that includes the fix.

Thanks,
Jimmy

NavigationEventArgs : no ExtraData in WPF?

Alastair — Tue, 17 May 2011 23:04:52 GMT

Hi Jimmy.

Still failing with no ExtraData. I grabbed the nightly from 13th May, sample with DLLs attached. Maybe I'm doing something odd?

All the best,

Alastair

NavigationEventArgs : no ExtraData in WPF?

Alastair — Tue, 17 May 2011 23:01:42 GMT

[moved post below]

NavigationEventArgs : no ExtraData in WPF?

jimmyps — Wed, 11 May 2011 11:39:05 GMT

Hi Alastair,

Thank you for providing a simple working sample.

Using the development's nightly build, it's confirmed that the OriginalUri is now captured properly. As the results, your application will automatically navigate to the Settings page after the successful login. This has been tested to work properly, and should exhibit identical behaviors and results as in the Silverlight counterpart.

The fixes for the ExtraData will be included in the upcoming hotfix scheduled later this month. If you preferred to receive the nightly build for early testing, please send an email to technical [at] intersoftpt.com and also please specify your subscription ID.

Thanks,
Jimmy

NavigationEventArgs : no ExtraData in WPF?

Alastair — Wed, 11 May 2011 04:18:00 GMT

Hi Jimmy,

I've attached a full sample. It's the vanilla Navigation app with authentication added. I picked apart the Silverlight samples and an earlier custom authentication sample on the boards. The examples are great by the way...

The authentication manager accepts "user" and "password" as a good credential. This is just for the example, obviously the backend authentication will be slightly stronger..;)

The settings page is set to require authentication: RequiresAuthentication="True"

When we navigate to Settings first time around, the LoginForm is invoked to get the credential. If this is successful, we return to the Home page, as the ExtraData doesn't contain the URI of the Settings page that invoked the form.

   public partial class LoginForm : UXPage
    {
        public LoginForm()
        {
            InitializeComponent();
        }
        // Executes when the user navigates to this page.
        protected override void OnNavigatedTo(NavigationEventArgs e)
        {
            // Get a reference to the NavigationService that navigated to this Page
            // If the login page was redirected from a protected page,
            // the e.ExtraData will include the URI of the original caller page.
            if (e.ExtraData != null && e.ExtraData is NavigationOptions)
            {
                // bind the URI to our view model, so we can redirect back 
                // to the original page when the login succeeded.
                LoginFormViewModel viewModel = this.DataContext as LoginFormViewModel;
                viewModel.OriginalUri = ((NavigationOptions)e.ExtraData).NavigateUri;
            }
        }
    }

We can then navigate manually to the Settings page, and it displays if the authentication was ok.

I was hoping to drop into the Settings page directly once the authentication is good:

            if (loginOperation.LoginSuccess)
            {
                // Login success, navigate to the page that originally requesting access
                
                // need to make ui calls on same thread as ui (sta threading model)
                // callback is created as a different thread
                // http://stackoverflow.com/questions/351676/problem-using-multithreading-with-simple-wpf-app 
                System.Windows.Application.Current.Dispatcher.Invoke(new System.Action(() => { NavigationServiceProvider.Navigate(this.OriginalUri); }));
            }

It's the OriginalUri not being set to SettingsPage because of no ExtraData. So we default to Home.

I'm pretty new to WPF - and as I said - ClientUI is an excellent product and making my life a lot easier. But I may have missed something obvious. Is there there a way to override the framework and provide the extra data myself?

All the best,

Alastair

NavigationEventArgs : no ExtraData in WPF?

jimmyps — Tue, 10 May 2011 11:00:48 GMT

Hello Alastair,

The only way to provide the extra data is through the 2nd parameter in the .Navigate method of the UXFrame. This conforms to the extra data passing mechanism in WPF navigation concept. However, there was a minor issue in the current build that prevent the extra data to be passed correctly in certain scenarios, this has been clarified fixed in the nightly development build.

While we're at the navigation topic, could you provide more information about the authentication issue that you're encountering? This will allow us to quickly shot the issues to be included into our monthly hotfix release.

Thanks,
Jimmy

NavigationEventArgs : no ExtraData in WPF?

Alastair — Sat, 07 May 2011 20:16:11 GMT

Hi,

I cannot for the life of me get any ExtraData when navigating from one page to the other. I've reduced this to a simple test on a vanilla "Basic Navigation Application (WPF)" project:

namespace ClientUIWPFNavApp1.Views 
{
    public partial class Settings : UXPage 
    {
        public Settings()
        {
            InitializeComponent();
        }
        // Executes when the user navigates to this page.
        protected override void OnNavigatedTo(NavigationEventArgs e)
        {
            if (e.ExtraData != null)
            {
                Console.WriteLine("OnNavigatedTo | e.ExtraData != null | Success!!");
            }
            else
            {
                Console.WriteLine("OnNavigatedTo | e.ExtraData == null | Failed!!");
            }
        }
    }
}

ExtraData is always null.

I'm putting together a single sign on, and this is preventing the login page from redirecting to the RequiresAuthentication="True" page on a good authentication.

Any help would be appreciated.

Thanks in advance,

Alastair