4 Answers, 1 is accepted
0
Hello Chulmin Yang,
I added the package ReactiveUI.WPF in a sample WPF application on our side, but I was not able to reproduce the misbehavior. That said, I would like to continue investigating the issue and try to provide a solution for you. To do that, I will need some help from you, in the form of a sample application that reproduces this scenario.
Than you for the cooperation in advance.
Regards,
Plamen Mitrev
Progress Telerik
I added the package ReactiveUI.WPF in a sample WPF application on our side, but I was not able to reproduce the misbehavior. That said, I would like to continue investigating the issue and try to provide a solution for you. To do that, I will need some help from you, in the form of a sample application that reproduces this scenario.
Than you for the cooperation in advance.
Regards,
Plamen Mitrev
Progress Telerik
0
Chulmin
Top achievements
Rank 1
Rank 1
answered on 05 Apr 2019, 07:54 AM
Hello Plamen Mitrev,
Thanks for your answer.
I try to upload sample application(13 MB), but it exceed the maximum attachment size (2 MB)
Could you tell me email adress or way to upload this file?
Thanks.
Regards
Chulmin Yang
0
Chulmin
Top achievements
Rank 1
Rank 1
answered on 05 Apr 2019, 09:26 AM
Hello Plamen Mitrev,
I found sample application that only add ReactiveUI.WPF package run record successfully. (C:\Users\admin\Desktop\WpfApp3.exe)
But same application in visual studio project directory(C:\Users\admin\Desktop\WpfApp3\WpfApp3\bin\Debug) fail to launch record. I guess permissions makes different results of two same applications.
It seems that using ReactiveUI.WPF package is not a reason for recording fail of our application.
I'm sorry to have confused you with the wrong information.
I will ask if I have another questions.
Thanks.
Regards
Chulmin Yang
I found sample application that only add ReactiveUI.WPF package run record successfully. (C:\Users\admin\Desktop\WpfApp3.exe)
But same application in visual studio project directory(C:\Users\admin\Desktop\WpfApp3\WpfApp3\bin\Debug) fail to launch record. I guess permissions makes different results of two same applications.
It seems that using ReactiveUI.WPF package is not a reason for recording fail of our application.
I'm sorry to have confused you with the wrong information.
I will ask if I have another questions.
Thanks.
Regards
Chulmin Yang
0
Hello Chulmin Yang,
Thank you for confirming that ReactiveUI.WPF is not causing the issues with recording.
You can check the WPF test configurations and ensure that the correct path, for the application under test, is set. Alternatively, you should be able to attach the recorder to a running instance of the WPF application and record the test steps.
As you have mentioned, it might be a permissions issue, as Test Studio requires administrator permissions to ensure that the recording and execution are not restricted. Try using the admin account on the machine with Test Studio and see if that makes a difference.
Please do not hesitate to contact us again.
Regards,
Plamen Mitrev
Progress Telerik
Thank you for confirming that ReactiveUI.WPF is not causing the issues with recording.
You can check the WPF test configurations and ensure that the correct path, for the application under test, is set. Alternatively, you should be able to attach the recorder to a running instance of the WPF application and record the test steps.
As you have mentioned, it might be a permissions issue, as Test Studio requires administrator permissions to ensure that the recording and execution are not restricted. Try using the admin account on the machine with Test Studio and see if that makes a difference.
Please do not hesitate to contact us again.
Regards,
Plamen Mitrev
Progress Telerik