Comments
Sort by recent activity
Hi,
Please try adding HtmlAgilityPack.HtmlDocument to the line-level timings block list. For more information, see: http://documentation.red-gate.com/display/APP9/Profiling+SecurityTransparent+and+partially-trusted+assemblies#ProfilingSecurityTransparentandpartially-trustedassemblies-block-list
Dom. / comments
Hi,
Please try adding HtmlAgilityPack.HtmlDocument to the line-level timings block list. For more information, see: http://documentation.red-gate.com/display/APP9/Profiling+SecurityTransparent+and+...
Hi,
This bug should be resolved by ANTS Performance Profiler 9.1, which we released earlier today.
Dom. / comments
Hi,
This bug should be resolved by ANTS Performance Profiler 9.1, which we released earlier today.
Dom.
Hi,
Thanks for your post and I'm sorry you're having problems with SmartAssembly.
Did you click 'Send Error Report'? If so, please can you PM me the email address you entered when you sent the report?
Can you also confirm you are using SmartAssembly 6.9, please? At the moment, I can't find any TypeInitializationExceptions for SmartAssembly 6.9 in our bug-tracking system, but we have received a few reports from SmartAssembly 6.7 and 6.8.
Thanks,
Dom. / comments
Hi,
Thanks for your post and I'm sorry you're having problems with SmartAssembly.
Did you click 'Send Error Report'? If so, please can you PM me the email address you entered when you sent the repo...
Hi Kelly,
Thanks very much for your post and very detailed video reproduction. Could you confirm whether you also get this when you are only profiling at method level (not line-level timings), please? If it does work with method-level timings only, you might have found a new variant of this known problem: https://documentation.red-gate.com/display/APP9/%27Common+language+runtime+detected+an+invalid+program%27+error+when+profiling
Most of the development team are now away until the New Year, but I'll try to get some more information for you when they are back.
Best wishes and Happy New Year,
Dom. / comments
Hi Kelly,
Thanks very much for your post and very detailed video reproduction. Could you confirm whether you also get this when you are only profiling at method level (not line-level timings), plea...
Hi,
This error happens if SmartAssembly tries to use a different version of the dependency. For example, if a different version of the Office Addin DLL is already in your GAC, SmartAssembly may try to use that incompatible version instead of the correct one. As the error message explains, you can normally solve this by using the MandatoryPath attribute.
For more information, see https://documentation.red-gate.com/disp ... pendencies
Thanks,
Dom. / comments
Hi,
This error happens if SmartAssembly tries to use a different version of the dependency. For example, if a different version of the Office Addin DLL is already in your GAC, SmartAssembly may try...
Hi,
Could you try removing the Castle.Core namespace from line-level timings, please? You can do that by going to C:UsersXXXXXXXXXXAppDataLocalRed GateANTS Performance Profiler 8, and adding <assemblyName>Castle.Core</assemblyName> to the LineLevelBlacklist.xml file. If that doesn’t work it might be worth trying excluding the whole of Castle.
For more information, please see https://documentation.red-gate.com/disp ... assemblies
Thanks,
Dom. / comments
Hi,
Could you try removing the Castle.Core namespace from line-level timings, please? You can do that by going to C:UsersXXXXXXXXXXAppDataLocalRed GateANTS Performance Profiler 8, and adding <asse...
Hi Cameron,
I'm sorry you're having problems with the new version of the profiler, and also apologies for the delay replying to you. Unfortunately, we didn't have the settings right on this forum, and so we missed your post until now.
If your application is aborting silently, it sounds like this could be difficult to investigate. I've asked our Support team to open a ticket for you, and they should be in touch shortly (but with the holiday season now close, I'm afraid there may be a further slight delay on this).
Dom. / comments
Hi Cameron,
I'm sorry you're having problems with the new version of the profiler, and also apologies for the delay replying to you. Unfortunately, we didn't have the settings right on this forum, ...
Hi,
Thanks for letting us know about this. Another customer has found the same problem. While we look into it, the other customer has suggested a workaround: 'Create a private method and move all code from the explicit interface implementation to this method.' Hopefully that will work for you too.
Dom.
(Internal reference for this bug: SA-1782) / comments
Hi,
Thanks for letting us know about this. Another customer has found the same problem. While we look into it, the other customer has suggested a workaround: 'Create a private method and move all c...
Hi CSXPJC,
'Should we be concerned about the .NET 4.5 assemblies that we have obfuscated using the command line?'
- No, the nature of the problem in SA 6.8 and earlier was that it would either fail to find the framework assemblies or it would work. If the command line tool output an assembly, therefore, they will have been obfuscated. You can check this using our Obfuscation Checker tool if you wish.
'Is the problem only in the UI or is it also in the command line version?'
- The problem was the SmartAssembly didn't know where to find the .NET 4.5 framework files in versions earlier than SmartAssembly 6.9. This would have affected both the UI and the command line. However, if you were running SmartAssembly from the command line, you probably already had a valid .saproj file that you called. If you happened not to reference the framework DLLs in that .saproj file, SmartAssembly might not have needed to find the .NET 4.5 DLLs, and in that case it would have worked.
As I say, SmartAssembly 6.9 contains full support for .NET 4.5 (including 4.5.1 and 4.5.2).
Dom. / comments
Hi CSXPJC,
'Should we be concerned about the .NET 4.5 assemblies that we have obfuscated using the command line?'
- No, the nature of the problem in SA 6.8 and earlier was that it would either fail...
Hi,
Early next week we expect to release SmartAssembly 6.9, which contains improved support for .NET 4.5, and also support for .NET 4.5.1 and 4.5.2.
This new release should resolve your problem.
Please click 'Check for updates' in SmartAssembly 6.8 next week to receive the update.
Dom. / comments
Hi,
Early next week we expect to release SmartAssembly 6.9, which contains improved support for .NET 4.5, and also support for .NET 4.5.1 and 4.5.2.
This new release should resolve your problem.
Pl...