Activity overview
Latest activity by StephenC
New SQL Backup Pro 7 early access forum - Please Read
The SQL Backup Pro 7 early access builds are now available to download from:http://help.red-gate.com/help/sql%20backup%207%20EAP/eap_download.htm
We have moved the early access support forum for SQ...
.NET Reflector 6.5 Early Access builds now available
There's an early version of .Net Reflector and .Net Reflector Pro which supports the C# 4 language changes now available.
The early access build also includes a number of bug fixes.
When you run th...
Visual Studio integration issues
If anyone is experiencing problems between Visual Studio and Reflector, please visit http://www.reflector.net and use the forum to report any issues.
As an immediate work-around you can easily unin...
How to uninstall the .Net Reflector Pro add-in
There are 2 very simple ways to remove the .NET Reflector Pro add-in from Visual Studio. If you can either:
- Use the add-in manager functionality in Visual Studio by going to Tools > Add-in Manage...
We have this in our system and we will be releasing a V5.2 at some point in the near future where this will most likely be fixed.
Sorry for the inconvenience at the moment and I'll update the post when the build/fix is released.
Stephen / comments
We have this in our system and we will be releasing a V5.2 at some point in the near future where this will most likely be fixed.
Sorry for the inconvenience at the moment and I'll update the post ...
Hi David,
just to clarify the first set of actions so we are definitely on the same page:
- take a snapshot
- group by namespace in the Class list
- expand a namespace until you find the class you are interested in
- create a Class Reference Graph for it
- go to the Instance list from one of the links in a node (or just jump to the instance list)
- Switch back to the Class List and the 'Group by Namespace' has been cleared
If i've followed it correctly i don't get the clearing of the checkbox. It takes me back to exactly the same place before I first left the Class List. The checkbox is still checked and the class for which i created the reference graph for is still selected.
Stephen / comments
Hi David,
just to clarify the first set of actions so we are definitely on the same page:
- take a snapshot
- group by namespace in the Class list
- expand a namespace until you find the class you ...
Participants needed for ANTS 6 usability feature testing
Fancy trying out some of the upcoming features of V6? We need participants to help usability test some of the upcoming features.
We are particularly looking for developers writing applications that...
ANTS Performance Profiler 6 EAP participants needed
if you are a .NET developer who has an application(s) that makes reasonable or heavy use of File I/O operations or there's a SQL Server component to your application we need you!
We have new builds...
Hi Mark,
that has actually been implemented for V6 of the Profiler.
We will be starting an early access program (maybe as soon as Friday but don't count on that) for V6 which will include the command line feature.
Stephen / comments
Hi Mark,
that has actually been implemented for V6 of the Profiler.
We will be starting an early access program (maybe as soon as Friday but don't count on that) for V6 which will include the comma...
Stack trace data isn't available in V5 of the memory profiler simply because of the massive overhead this causes to record and we wanted to concentrate on making an extremely low overhead profiler for V5 which is in some ways more geared towards memory leak finding although not necessarily.
There is a section at the bottom of the Summary tab indicating when heap fragmentation is a likely cause of problems being observed.
Using the Class Reference graph is also often helpful in combination with filters to identify objects which are referncing other classes for you to determine objects that should be reduced.
We are considering recording stack trace information for V6 although for a large % of people the overhead and impact on the application being profiled will be too high to make it a useful feature.
Stephen / comments
Stack trace data isn't available in V5 of the memory profiler simply because of the massive overhead this causes to record and we wanted to concentrate on making an extremely low overhead profiler ...