Performance Profiler Version 2 of the add-in supports Visual Studio 2010 and later. If you installed your .NET Bundle before July 17th 20
/app8/setting-up-and-running-a-profiling-session/using-the-visual-studio-add-in
, ie, the largest fragment is fairly small. Fragmentation may be causing .NET to reserve too much free memory. The free space ratio is gre
is fairly small. Memory fragmentation may be causing .NET to reserve too much free memory. The free space ratio is greater than 0.7:1, an
does not support SQL Server 2005, as of 3.2.0 neither does SQL Dependency Tracker SQL Dependency Tracker now requires .NET Framework 4.7.
/sdt3/release-notes-and-other-versions/sql-dependency-tracker-3-2-release-notes
. (An exception to this is assembly-signing tools, if you choose not to sign your code with SmartAssembly). Automatic integration (.NET Fr
/sa8/building-your-assembly/using-smartassembly-with-msbuild
it was possible to execute code by selecting a source assembly containing a .NET object with an embedded resource file. (CVE-2018-14581)
/sa8/release-notes-and-other-versions/smartassembly-6-12-release-notes
application uses. (Not available in Windows XP / Server 2003 and earlier, or when profiling .NET 1.1 applications.) This option will slow
the GC.Collect method, which runs the .NET garbage collector. ANTS Memory Profiler then collects information about the objects that survi
are not available when profiling a .NET 1.1 application. Filters that can help focus on a specific part of your application The following
/amp8/working-with-profiling-results/object-filters/suggestions-for-using-filters
Profiler. Version 2 of the add-in supports Visual Studio 2010 and later. If you installed your .NET Bundle before July 17th 2014, you hav
/amp8/setting-up-a-profiling-session/using-the-visual-studio-add-in
amp_new_profiling_session_button.png From the list of application types, select .NET executable. Enter the path to sllauncher.exe - e.g.
Gate\SmartAssembly 7\SDK\Exception Reporting\, then build the assembly as a DLL. For .NET Core applications, you should use .NET Standard
/sa7/setting-up-error-reporting/error-reporting-with-the-sdk
(this dependency will be removed when processed). For .NET Core applications, you should use .NET Standard version of the SDK assembly, l
it was possible to execute code by selecting a source assembly containing a .NET object with an embedded resource file. (CVE-2018-14581)
/sa7/release-notes-and-other-versions/smartassembly-6-12-release-notes
with the error : Method not found: 'UInt32 <Module>._ANTS_Begin_Sql(System.String)' This error is caused by a bug in the .NET profiling A
/app10/troubleshooting/error-messages/method-not-found-uint32-module-_ants_begin_sql-system-string
When using ANTS Memory Profiler or ANTS Performance Profiler, you may find that you cannot attach to any .NET 4 process. This can be caus
with the error : Method not found: 'UInt32 <Module>._ANTS_Begin_Sql(System.String)' This error is caused by a bug in the .NET profiling A
/app11/troubleshooting/error-messages/method-not-found-uint32-module-_ants_begin_sql-system-string
When using ANTS Memory Profiler or ANTS Performance Profiler, you may find that you cannot attach to any .NET 4 process. This can be caus
Performance Profiler 7.4, C#5 has been released, which includes the new async and await keywords that are supported by .NET 4.5. We've wo
can't attach to a .NET 4+ process when the process is a Windows Store app. You can't profile File I/O when profiling Windows Store apps.
/app8/release-notes-and-other-versions/ants-performance-profiler-8-0-release-notes
disk space .NET framework requirements The graphical user interface requires Microsoft .NET version 2, 3.0 or 3.5 http://www.microsoft.co
). /cassiniNetVersion:<cassiniNetVersion> (Alias: /cnv) If Visual Studio 2010 or later is installed, this is the version of .NET to use wh
/app9/setting-up-and-running-a-profiling-session/profiling-from-the-command-line-api
, or if you prefer, bypass IE and use the "shim" provided by Windows. To profile a ClickOnce application using Internet Explorer, use the
running, the following error entry is written to the application event log: Source: .NET Runtime Category: None Event ID: 1022 Descriptio
/app9/troubleshooting/error-messages/failed-to-cocreate-profiler
February 8th, 2017 New features Added support for profiling .NET Core 1.0 applications. Licensing changes We've made changes to the way l
/amp8/release-notes-and-other-versions/ants-memory-profiler-8-11-release-notes
