Better Software Quality with Visual Studio Team System 2010

Great demo. So when can we get the CTP bits????
Bob Hanson
Blind feedback: Before watching the video (dinner first), I want my 3rd party .Net language to be able to create historical snapshots (or whatever they're called). For example, traditionally, programmer errors would occur before and after file open statements or when spawning processes. Can my runtime tell the debugger to create a snapshot and name it? How will histroical debugging be exposed for 3rd party languages?
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.
This seems to be only available for VSTS developers.... or am I just not seeing it? Is there a plan to push this out to all us poor development shops who aren't on VSTS? I'm dieing to use this feature!!
Microsoft needs to provide support for this feature in the Professional Version of Studio.
This is an idea whose time has come. I believe that this kind of things will replace logging. Logging clutters up code, slows down performance always (even if to see if it's turned on), and even when used copiously never seems to actually capture the state
that's needed. Recorded debugging is the future! Mu ha ha ha
Now about VS 2010's feature. What I've seen so far seems to indicated that the user can't place their own "diagnostic events" (breakpoints) anywhere they need. Without this, the feature suffers from the same problem as logging... the capture points are arbitrary. I would like to set a bunch of breakpoints, each with a set of watches (expecially with expressions like I can normally), then be able to send this capture data to any location running my code (e.g. live running apps), capture the data, then send it back and walk through it in the IDE. It would be one of the biggest advances in programmer productivity in years!
Best,
--
Nathan Allan
Database Consulting Group
Looking forward for native C++ support!
Hi there,
we are only working with native code (C++).
When will these features (historical debugging, code analysis, impact tests) be available for C++ developers?
Thanks,
Andi