Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » versioning   (RSS)

Debugger and Versioning link fest

I've had enough "Debugger + Versioning" posts to go back and create a versioning category. The general overview: Managed Debugging Versioning . This provides the ground rules and key concepts for how managed debugging versioning works. Implications of
Posted by jmstall | 1 Comments
Filed under: ,

What can I use to debug VC2002 Managed C++ apps?

Debugging MC++ apps from VC2002 with VS2005 came up in the comments here . In the ideal world, Whidbey works great and everybody is upgraded to Whidbey (VS2005) and so nobody is still interested in VC2002. In our broken and fallen world, these ideals
Posted by jmstall | 5 Comments
Filed under:

Debugger and Versioning

"Which versions of a managed debugger (eg, Visual Studio) can debug which versions of the CLR? And How?" This is the fundamental debugger versioning question. Here is the "debugging stack" from a versioning perspective, including the protocols between
Posted by jmstall | 5 Comments
Filed under:

Put a config file on your debuggers

VisualStudio.Net 2003 has a config file saying that it's for V1.1 CLR. If you write your own V1.1 debugger, you should do that too. One big motivation is to ensure your V1.1 debugger creates the V1.1 implementation of ICorDebug. In V1.1, ICorDebug was
Posted by jmstall | 0 Comments
Filed under:

"Visual Studio 2003 Mixed Mode Debugging Crash"

It's great that 2005 has shipped. I personally enjoy using it for my own pet projects and I'm very pleased. But shipping a V2 also means exposing versioning problems in the V1 design. Such an issue came up on the forums , which basically boils down to:
Posted by jmstall | 8 Comments

VS 2003 can not debug .NET 2.0 apps.

Somebody asked here on the forums if you can use VS 2003 to debug .NET 2.0 (whidbey) apps. Unfortunately, the answer is no. VS 2003 can not debug .NET 2.0 apps. It is a restriction in the underlying .NET debugging services (see below) You can still use
 
Page view tracker