Comments
Sort by recent activity
Even being taken to declaring source file would be already of great help. But I guess that the profiler has enough information available to even offer a selection of a) where the object in question was actually created, b) which ctors where used to do so, and then take me to any of those.
Taking it a step further it could even apply the same scheme used by VisualAssist and offer pseudo-source access throught the available meta data for assemblies without source code, for system types and imported assemblies. / comments
Even being taken to declaring source file would be already of great help. But I guess that the profiler has enough information available to even offer a selection of a) where the object in question...
No, no, I am really taken to the wrong source file. The file shows does not even create a single instance of the questionable object.
Rebuilding does not fix the problem. / comments
No, no, I am really taken to the wrong source file. The file shows does not even create a single instance of the questionable object.
Rebuilding does not fix the problem.
No, is a windows forms desktop application, heavily database dependant, C# 2.0, .Net 2.0, using VS2005 SP2. / comments
No, is a windows forms desktop application, heavily database dependant, C# 2.0, .Net 2.0, using VS2005 SP2.
Will verify, but i guess so, since usually we do a rebuild all before testing. I keep you informed as we go. / comments
Will verify, but i guess so, since usually we do a rebuild all before testing. I keep you informed as we go.
Right click in any source code window inside the IDE, brings up the editor context menu. Among other entries it contains 3 entries from the ANTS Profiler - Profile Method, Profile Class, Profile Namespace.
Those entries make not much sense during a debug session. / comments
Right click in any source code window inside the IDE, brings up the editor context menu. Among other entries it contains 3 entries from the ANTS Profiler - Profile Method, Profile Class, Profile Na...