To add to Brian's point about 64-bit support, in the F5 scenario, our collection mechanism (i.e. how we collect information about a process) is specific to 32-bit processes. Unfortunately, we didn't have enough time to implement 64-bit support and had to
make a hard cut. You can bet that 64-bit support is one of our top priorities after the VS2010 release.
In VS 2010, the Historical Debugger feature will work for C++/CLI, but not for native C++. This was a really difficult decision for us but we are thinking hard about how to address this in the future.
We are working towards having a solution where you don't need VS installed to be able to collect a log file for the Historical Debugger. We haven't finalized a plan yet, so I can't go into detail about what the final experience will be.
Habib Heydarian
Comments
10-4 Episode 28: An Introduction to the Historical Debugger
The scope of the work to support 64-bit won't fit into a SP. It would be the version after VS2010 but I don't know the exact timeline.
HabibH.
10-4 Episode 28: An Introduction to the Historical Debugger
To add to Brian's point about 64-bit support, in the F5 scenario, our collection mechanism (i.e. how we collect information about a process) is specific to 32-bit processes. Unfortunately, we didn't have enough time to implement 64-bit support and had to make a hard cut. You can bet that 64-bit support is one of our top priorities after the VS2010 release.
Thanks,
Habib Heydarian.
10-4 Episode 20: Downloading and Installing Visual Studio 2010 Beta 1
Thanks for the feedback Moemeka. We don't have any code analysis rules for dynamic. Do you have any specific scenarios in mind?
HabibH.
Historical Debugger and Test Impact Analysis in Visual Studio Team System 2010
In VS 2010, the Historical Debugger feature will work for C++/CLI, but not for native C++. This was a really difficult decision for us but we are thinking hard about how to address this in the future.
Thanks,
HabibH.
Historical Debugger and Test Impact Analysis in Visual Studio Team System 2010
We are working towards having a solution where you don't need VS installed to be able to collect a log file for the Historical Debugger. We haven't finalized a plan yet, so I can't go into detail about what the final experience will be.
Thanks,
HabibH.