This is a migrated thread and some comments may be shown as answers.

Crash when calling Notify

5 Answers 64 Views
RateApplicationReminder
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Oliver
Top achievements
Rank 1
Oliver asked on 21 Jul 2013, 11:56 AM
protected override void OnNavigatedTo(System.Windows.Navigation.NavigationEventArgs e)
{
    base.OnNavigatedTo(e);

    try
    {
        rateReminder = new RadRateApplicationReminder();
        rateReminder.RecurrencePerUsageCount = 1;
        rateReminder.SkipFurtherRemindersOnYesPressed = true;
        rateReminder.ReminderClosed += OnRateReminderReminderClosed;
        rateReminder.AllowUsersToSkipFurtherReminders = false;
        rateReminder.Notify();
    }
    catch (Exception)
    {
    }
}

The code above crashes with a COMException. Any suggestions? I'm on the latest official build.

5 Answers, 1 is accepted

Sort by
0
Deyan
Telerik team
answered on 24 Jul 2013, 11:33 AM
Hello Oliver,

Thanks for writing and for sharing your code.

We are currently not able to reproduce the issue on our side. Could you please isolate the case in a sample project and send it to us for further investigation? If that's not possible, could you please describe the scenario in simple steps so that we can try to reproduce it here?

You will have to open a new support ticket in order to be able to attach files in case you want to.

Thanks for your time.

Regards,
Deyan
Telerik
Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
0
Oliver
Top achievements
Rank 1
answered on 26 Jul 2013, 10:08 AM
In fact the call crashes with an InvalidOperationException: ApplicationRuntimeHelper should be initialized before using this component.
0
Todor
Telerik team
answered on 29 Jul 2013, 02:13 PM
Hello Oliver,

Please have a look at the documentation article here, which explains how to initialize the ApplicationUsageHelper.

Let me know if you need additional assistance.

Regards,
Todor
Telerik
Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
0
Waleed
Top achievements
Rank 1
answered on 09 Oct 2013, 01:38 PM
Hi,
I confronted the same problem. Initialization  of ApplicationUsageHelper solved the problem

Private Sub Application_Launching(ByVal sender As Object, ByVal e As LaunchingEventArgs)
    ApplicationUsageHelper.Init("1.1")
End Sub
 
 Private Sub Application_Activated(ByVal sender As Object, ByVal e As ActivatedEventArgs)
    ApplicationUsageHelper.OnApplicationActivated()
End Sub

P.S: The value of version number didn't affect the workability of the app.
0
Todor
Telerik team
answered on 14 Oct 2013, 11:35 AM
Hello Waleed,

Yes, the ApplicationUsageHelper must be initialized before using RadRateApplicationRemider. It is an application component which is also used by other components, for example RadDiagnostics. When RadDiagnostics reports that an exception has occurred, the report contains the version number that you have used to initialize the ApplicationUsageHelper. This information can help you identify which was the version that crashed so you can easier find the cause for the issue.

Regards,
Todor
Telerik
Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
Tags
RateApplicationReminder
Asked by
Oliver
Top achievements
Rank 1
Answers by
Deyan
Telerik team
Oliver
Top achievements
Rank 1
Todor
Telerik team
Waleed
Top achievements
Rank 1
Share this question
or