Forum Discussion
dnimrevo
14 years agoNew Contributor
Hi Irina,
Thank you for your suggestions. Let me tell you my experiences attempting each of them:
- I tried to use the AQTime Troubleshooter, but after it asked me two questions it asked me to send a report to the support team. Since I only have the Standard version, it didn't let me send the report to the support team.
- I tried to reproduce the problem in AQTime Pro, but was unable to. AQTime Pro forced me to uninstall the Standard version, but after I finally installed the Pro one, I didn't find any way to get the trial key. I must have missed it somewhere, because it kept sending me to a page in the smartbear website where I was supposed to login with some Customer ID I don't have.
- Finally I attempted to create a more simple application where the problem could be reproduced, but after re-installing AQTime Standard, the problem was gone. After some investigation I found out that if I changed the compilation of my application to 64bits, AQTime could properly profile it. I don't really know why, since other .NET applications I have in 32 bits are profiled normally.
Anyway, my problem is solved, so thank you once again.
Thank you for your suggestions. Let me tell you my experiences attempting each of them:
- I tried to use the AQTime Troubleshooter, but after it asked me two questions it asked me to send a report to the support team. Since I only have the Standard version, it didn't let me send the report to the support team.
- I tried to reproduce the problem in AQTime Pro, but was unable to. AQTime Pro forced me to uninstall the Standard version, but after I finally installed the Pro one, I didn't find any way to get the trial key. I must have missed it somewhere, because it kept sending me to a page in the smartbear website where I was supposed to login with some Customer ID I don't have.
- Finally I attempted to create a more simple application where the problem could be reproduced, but after re-installing AQTime Standard, the problem was gone. After some investigation I found out that if I changed the compilation of my application to 64bits, AQTime could properly profile it. I don't really know why, since other .NET applications I have in 32 bits are profiled normally.
Anyway, my problem is solved, so thank you once again.
Related Content
- 12 years ago
- 4 years ago
Recent Discussions
- 7 months ago
- 2 years ago