Comments
Sort by recent activity
Hi,
Yes, I'm afraid this is a known bug in ANTS Performance Profiler 7.4 and lower, related to scaling in high DPI modes. Sorry about that.
I'm pleased to tell you, however, that the startup screen and other parts of the Performance Profiler are being completely redesigned for v. 8.0, and (because we're now using WPF) this bug is fixed.
We're still a few weeks away from releasing v. 8.0, but you can download the beta from http://www.red-gate.com/labs/ants-performance-profiler/. We'd be glad to hear your feedback on the new screen.
Dom. / comments
Hi,
Yes, I'm afraid this is a known bug in ANTS Performance Profiler 7.4 and lower, related to scaling in high DPI modes. Sorry about that.
I'm pleased to tell you, however, that the startup screen...
The beta program is still open, and we're still interesting in hearing your feedback on ANTS Performance Profiler 8.0.
Features added in the last few builds of the beta include:
* Web request profiling
* Sharepoint 2013 support
If you are profiling web applications, the Performance Profiler also now starts your default browser, not just Internet Explorer, by default. This is one of the most requested features from users, so we're really pleased to have been able to do this.
For more information, please see http://www.red-gate.com/labs/ants-performance-profiler/ / comments
The beta program is still open, and we're still interesting in hearing your feedback on ANTS Performance Profiler 8.0.
Features added in the last few builds of the beta include:
* Web request prof...
Thanks for your feedback. I've added this request to our bug system, where it has internal reference PP-2259. Unfortunately, I can't promise an immediate fix but it will be considered when we are planning the next version. / comments
Thanks for your feedback. I've added this request to our bug system, where it has internal reference PP-2259. Unfortunately, I can't promise an immediate fix but it will be considered when we are p...
I'm pleased to announce that we've just released ANTS Performance Profiler 7.4, which fixes the issue I described above.
If you are affected by this problem, you can upgrade your copy of the Profiler:
On the Help menu, click Check for Updates... / comments
I'm pleased to announce that we've just released ANTS Performance Profiler 7.4, which fixes the issue I described above.
If you are affected by this problem, you can upgrade your copy of the Profil...
Hi Josh,
Sorry for the delay in replying while I was on vacation last week.
If I understand your comments correctly, your problem is with ANTS Memory Profiler 7.4, not ANTS Performance Profiler. I'm afraid the Memory Profiler doesn't currently support Silverlight 5, and there's also a known bug where (as you say), the add-in in Visual Studio 2012 launches the wrong version of the Web Development server.
Both of these issues were fixed in the recently-released ANTS Performance Profiler 8.0 and we'll endevor to get these fixes into the earliest betas of ANTS Memory Profiler 8.0 once we open that beta program shortly. / comments
Hi Josh,
Sorry for the delay in replying while I was on vacation last week.
If I understand your comments correctly, your problem is with ANTS Memory Profiler 7.4, not ANTS Performance Profiler. I'...
Hi, doyle_am: In your case, this is probably due to the fact that ANTS Performance Profiler 7.3 does not support Visual Studio 2012. If you have already installed VS2012, ANTS Performance Profiler will attempt to use the VS2012 version of the WebDev server, even if you launch the profiler from VS2010.
I'm pleased to say that ANTS Performance Profiler 7.4 will support VS2012, and so this issue is fixed. Version 7.4 is due for release in the coming weeks but if you'd like a private build (untested), please PM me and I'll send you a link.
Dom / comments
Hi,doyle_am: In your case, this is probably due to the fact that ANTS Performance Profiler 7.3 does not support Visual Studio 2012. If you have already installed VS2012, ANTS Performance Profiler w...
To find the version number, in the left-hand menu in SmartAssembly, click 'About SmartAssembly'
If you need to upgrade to SmartAssembly 6.7, also in the left-hand menu, click 'Check for Updates'.
Let us know if this doesn't resolve your problem. / comments
To find the version number, in the left-hand menu in SmartAssembly, click 'About SmartAssembly'
If you need to upgrade to SmartAssembly 6.7, also in the left-hand menu, click 'Check for Updates'.
L...
Hi,
I've just released SmartAssembly 6.6.4.95, which includes this fix. To download it, use 'Check for Updates' in SmartAssembly's menu.
Thanks for telling us about the bug.
Dom. / comments
Hi,
I've just released SmartAssembly 6.6.4.95, which includes this fix. To download it, use 'Check for Updates' in SmartAssembly's menu.
Thanks for telling us about the bug.
Dom.
Hi,
For Automatic Error Reporting, yes, your solution is the best one: create a custom template using the UnhandledExceptionHandler and only report if some saved setting is set.
For Feature Usage Reporting, the best thing to do would be to set the registry key that the other templates provided by SmartAssembly would normally set when consent is given. That registry key is HKEY_CURRENT_USER\Software\[CompanyName]\[ApplicationName]\SmartAssemblyReportUsage Set the value to True if the user gives consent, or set it to False if the user does not consent. Use the Automatic template as normal. Features are not reported by the Automatic template if the value of this key is False. Note: this is not accurate. See the correction post below.
Best wishes,
Dom. / comments
Hi,
For Automatic Error Reporting, yes, your solution is the best one: create a custom template using the UnhandledExceptionHandler and only report if some saved setting is set.
For Feature Usage R...
Hi again,
The developers have just informed me that the Automatic template for Feature Usage Reporting doesn't in fact respect the registry key mentioned above. So your solution of using a custom template with the UsageReporter class is required.
Sorry for the confusion.
Dom. / comments
Hi again,
The developers have just informed me that the Automatic template for Feature Usage Reporting doesn't in fact respect the registry key mentioned above. So your solution of using a custom t...